約 6,885,619 件
https://w.atwiki.jp/it_certification/pages/163.html
1. 目的 2. 構成2.1. 設定概要 2.2. 構成図 2.3. netファイル 2.4. 初期設定 3. [検証] http serverへの接続3.1. デフォルト設定の確認 3.2. http serverへの接続 4. [検証] https serverへの接続4.1. https serverの有効化 4.2. https serverへの接続 5. [検証] enable passwordによる認証5.1. enable passwordの設定 5.2. 認証の確認 6. [検証] ローカルデータベースによる認証6.1. ローカルデータベールによる認証設定 6.2. ユーザの作成 6.3. privilege 15による接続 6.4. privilege 7による接続 6.5. privilege 1による接続 7. [検証] http serverの無効化7.1. http severの無効化 7.2. 無効化の確認 1. 目的 http serverによる接続方法を確認します。 2. 構成 2.1. 設定概要 ルータの初期設定はIPアドレスのみです。 2.2. 構成図 2.3. netファイル model = 3660 [localhost] [[3660]] image = C \Program Files\Dynamips\images\c3660-ik9o3s-mz.124-6.T.bin ram = 128 [[ROUTER R1]] f0/0 = NIO_gen_eth \Device\NPF_{8B89D910-5ED3-4A43-9DE9-6A272A3D7592} 2.4. 初期設定 R1 ! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname R1 ! boot-start-marker boot-end-marker ! ! no aaa new-model ! resource policy ! memory-size iomem 5 ! ! ip cef no ip domain lookup ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0 ip address 192.168.200.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! ip http server no ip http secure-server ! ! ! no cdp run ! ! ! control-plane ! ! ! ! ! ! ! ! ! line con 0 line aux 0 line vty 0 4 ! ! end 3. [検証] http serverへの接続 3.1. デフォルト設定の確認 http serverがデフォルトで有効になっているかを確認します。 R1#show running-config | include ip http ip http server no ip http secure-server R1# もし無効になっている場合は以下の通り入力し、http serverを有効にします。 R1(config)#ip http server 3.2. http serverへの接続 ブラウザに以下URLを入力し、http serverに接続できる事を確認します。 http //192.168.200.1/ 以下の画面が表示される事を確認します。 4. [検証] https serverへの接続 4.1. https serverの有効化 以下の通り入力し、https serverを有効にします。 R1(config)#ip http secure-server % Generating 1024 bit RSA keys, keys will be non-exportable...[OK] R1(config)# *Mar 1 00 18 55.475 %SSH-5-ENABLED SSH 1.99 has been enabled *Mar 1 00 18 57.071 %PKI-4-NOAUTOSAVE Configuration was modified. Issue "write memory" to save new certificate R1(config)# 4.2. https serverへの接続 ブラウザに以下URLを入力し、http serverに接続できる事を確認します。 https //192.168.200.1/ 以下の画面が表示される事を確認します。 5. [検証] enable passwordによる認証 5.1. enable passwordの設定 http (https) serverの認証方針は以下の通り選択する事ができますが、デフォルトではenable passwordによる認証を行います。 R1(config)#ip http authentication ? enable Use enable passwords local Use local username and passwords 以下の通りenable passwordを定義します。 R1(config)#enable secret cisco 5.2. 認証の確認 ブラウザに以下URLを入力し、認証を求められる事を確認します。 http //192.168.200.1/ なお、パスワードは「cisco」で、ユーザ名は何を入力しても構いません。 6. [検証] ローカルデータベースによる認証 6.1. ローカルデータベールによる認証設定 ローカルデータベースで認証するよう、以下の設定を投入します。 R1(config)#ip http authentication local 6.2. ユーザの作成 以下の3ユーザを作成します。なお、privilegeを省略すると privilege 1になります。 R1(config)#username one privilege 15 password one R1(config)#username two privilege 7 password two R1(config)#username three password three 6.3. privilege 15による接続 ユーザoneで以下URLに接続できる事を確認します。 http //192.168.200.1/ 6.4. privilege 7による接続 ユーザtwoで以下URLへの接続を試みると、認可でエラーを返される事を確認します。 http //192.168.200.1/ ユーザtwoで以下URLへの接続が可能である事を確認します。 http //192.168.200.1/level/07/ 6.5. privilege 1による接続 ユーザthreeで以下URLへの接続が可能である事を確認します。 http //192.168.200.1/level/01/ 7. [検証] http serverの無効化 7.1. http severの無効化 http serverおよび http secure-serverを無効にします。 R1(config)#no ip http server R1(config)#no ip http secure-server 7.2. 無効化の確認 以下URLをブラウザに入力し、http serverが無効化されている事を確認します。 http //192.168.200.1/
https://w.atwiki.jp/mydefrag_jp/pages/17.html
FileBoolean FileBoolean (...) All Archive AverageFragmentSize Compressed CreationDate Directory DirectoryName DirectoryPath Encrypted FileLocation FileName FragmentCount Fragmented FullPath Hidden ImportListFromFile ImportListFromProgramHints Largest LargestFragmentSize LastAccess LastAccessEnabled LastChange NOT NotToBeIndexed Offline OR Readonly SelectNtfsSystemFiles Size SmallestFragmentSize Sparse System Temporary Virtual 原文 http //www.mydefrag.com/Scripts-FileBoolean.html 更新日 2010/12/12 (ここで取り扱っている内容の原文をコピーした日付です) (...) Combine file booleans into a single boolean. Syntax ( FILEBOOLEAN ) Example FileSelect Size(10000000,0) and ( Name("-.zip") or Name("-.arj") ) FileActions ... FileEnd See also FileSelect FileBoolean FileActions All Select all the items (files, directories) that have not yet been placed in a previous zone. Syntax all Example FileSelect All FileActions ... FileEnd See also FileSelect FileBoolean FileActions Archive Select all the items that have the "archive" attribute set (yes) or not set (no). Applications use this attribute to mark files for backup or removal. Syntax Archive(yes) Archive(no) Example FileSelect # Select all the items that have the "archive" attribute. Archive(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions AverageFragmentSize Select all the items that have an average number of bytes per fragment between the minimum (first number) and the maximum (second number). If the second number is zero then the maximum is infinity. For example, if an item is 300 bytes in size and has 3 fragments then it has an average fragment size of 100 bytes. Syntax AverageFragmentSize(NUMBER , NUMBER) Example FileSelect # Select all the items that have an average fragment size between 100 and 1000 bytes. AverageFragmentSize(100,1000) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Compressed Select all the items that have the "compressed" attribute set (yes) or not set (no). For a file the attribute indicates if the file is compressed by the build-in Windows compression. For directories the attribute is the default for new files (directories by themselves cannot be compressed). Syntax Compressed(yes) Compressed(no) Example FileSelect # Select all the items that are compressed with the built-in Windows compression. Compressed(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions CreationDate Select all the items that were created between the minimum time (first parameter) and the maximum time (second parameter). If the first parameter is empty then the minimum time is the beginning of time. If the second parameter is empty then the maximum time is infinity. - The creation date can be newer than the last-changed date, for example when a file was downloaded, or unpacked from an archive (such as zip or arj). Syntax CreationDate(DATETIME , DATETIME) Example FileSelect # Select all the items that were created less than 10 days ago. CreationDate(10 days ago,now) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Directory Select all the directories (yes) or all the other files (no). Please note that this boolean does not select the files in a directory, but the directory itself. Directories and files are separate entities. Directories cannot be moved (defragmented, optimized) on FAT32 volumes. This is a known limitation of the Windows defragmentation API and not a bug in MyDefrag. Moving directories is slower than moving files of the same size, presumably because Windows has to update indexes and links in the MFT. Syntax Directory(yes) Directory(no) Example FileSelect # Select all the directories. Directory(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions DirectoryName STRINGにマッチする名前を持つディレクトリをすべて選択し、そのディレクトリ以下にあるすべてのファイルとサブディレクトリを選択します。 STRINGにはワイルドカードとして"*"(0文字以上の任意の文字)と"?"(１文字の任意の文字)を選択できます STRINGにはスラッシュ・バックスラッシュ(および\マーク)を含めないでください。これはすべてのファイルのファイル名について比較しますが、このファイル名には(ファイルパスではないので)スラッシュなどが含まれていません。 この関数はすべてのハードリンク ファイル名を一つのアイテム(二つ名を持ち、同時に違う場所に存在するが、その実体は同じファイル)として扱います。ログファイルには最初に見つかった名前が載ります, so it may appear as if the function has selected some wrong items. この関数はソフトリンク(ジャンクション・シンボリックリンク）を追従しません。 Syntax DirectoryName(STRING) Example FileSelect # Select everything in the "Program Files" directory. DirectoryName("Program Files") FileActions .... FileEnd See also DirectoryPath FileName FullPath FileSelect FileBoolean FileActions DirectoryPath STRINGにマッチするフルパスを持つディレクトリをすべて選択します、そしてそのディレクトリ以下にあるすべてのファイルとサブディレクトリを選択します。STRINGにはワイルドカードとして"*"(0文字以上の任意の文字)と"?"(１文字の任意の文字)を選択できます。 この条件構文はDirectoryName()とよく似ていますが、これはディレクトリ名ではなくフルパスで比較するために多少遅いです。 STRINGはディレクトリのフルパスと比較され、マッチするでしょう。(The STRING is compared with and must match the full path of the directories.) ドライブレターにマッチするようなマスクを確認してください。ディレクトリパスというのは"c \windows\System32"といったような物のことです。バックスラッシュの追跡はしないことを覚えておいてください。(訳注 自信がないのでエロイ人お願いします。) この関数はすべてのハードリンク ファイル名を一つのアイテム(二つ名を持ち、同時に違う場所に存在するが、その実体は同じファイル)として扱います。ログファイルには最初に見つかった名前が載ります, so it may appear as if the function has selected some wrong items. この関数はソフトリンク(ジャンクション・シンボリックリンク）を追従しません。 Syntax DirectoryPath(STRING) Example FileSelect # Select everything in the "? \Program Files" directory. DirectoryPath("? \Program Files") FileActions .... FileEnd See also DirectoryName FileName FullPath FileSelect FileBoolean FileActions Encrypted Select all the items that have the "encrypted" attribute set (yes) or not set (no). For a file the attribute indicates if the file is encrypted by the build-in Windows encryption. For directories the attribute is the default for new files (directories by themselves cannot be encrypted). Syntax Encrypted(yes) Encrypted(no) Example FileSelect # Select all the items that have the "encrypted" attribute. Encrypted(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions 原文 http //www.mydefrag.com/Scripts-FileBoolean.html 更新日 2010/12/12 (ここで取り扱っている内容の原文をコピーした日付です) FileLocation Select the items (files, directories) that are located in a specified area on the disk. The ARGUMENT specifies one of several options to choose from, the first NUMBER is the beginning of the area and the second NUMBER the end, both in LCN (Logical Cluster Number). If the first NUMBER is zero then the area begins at the beginning of the disk. If the second NUMBER is zero then the area ends at the end of the disk. Syntax FileLocation(ARGUMENT , NUMBER , NUMBER) Argument Possible values for ARGUMENT BeginOfFile Select files if the beginning of the file is inside the area. EndOfFile Select files if the end of the file is inside the area. EntireFile Select files that have all their data inside the area. AnyPart Select files if any of their data is inside the area. AnyCompleteFragment Select files if at least 1 complete fragment is inside the area. Example # Highlight files from the beginning of the disk up to LCN=10000. SetFileColor(FileLocation(EntireFile,0,10000),all,255,255,255) See also FileSelect FileBoolean FileActions FileName STRINGにマッチするファイル名を持つファイルやディレクトリといったアイテムすべてを選択します。 STRINGにはワイルドカートとして*と?(ry)を含められます。 STRINGにはスラッシュやバックスラッシュ(および\円マーク)を含めないでください。すべてのファイル名について比較しますが、このファイル名にはスラッシュなどは含まれません。 この関数はすべてのハードリンク ファイル名を一つのアイテム(二つ名を持ち、同時に違う場所に存在するが、その実体は同じファイル)として扱います。ログファイルには最初に見つかった名前が載ります, so it may appear as if the function has selected some wrong items. この関数はソフトリンク(ジャンクション・シンボリックリンク）を追従しません。 Syntax FileName(STRING) Example FileSelect FileName("*.mp3") FileActions .... FileEnd See also DirectoryPath DirectoryName FullPath FileSelect FileBoolean FileActions FragmentCount Select all the items that have a number of fragments between the minimum (first number) and the maximum (second number). If the second number is zero then the maximum is infinity. Syntax FragmentCount(NUMBER , NUMBER) Example FileSelect # Select all the items that have at least 3 fragments and at most 10 fragments. FragmentCount(3,10) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Fragmented Select all the items that are fragmented(yes) or not fragmented(no). Syntax Fragmented(yes) Fragmented(no) Example FileSelect # Select all the fragmented items. Fragmented(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions FullPath STRING1にマッチするフルパスを持つディレクトリをすべて選択します。また、そのディレクトリ以下でSTRING 2にマッチするすべてのディレクトリとサブディレクトリが選択されます。 STRING1/2にはワイルドカード"*" "?" (ry)が使用できます。 ドライブレターにもマッチするようにディレクトリマスクを書いてください。 ディレクトリパスとは "c \windows\System32"のような物のことです。ノート バックスラッシュは追跡しません。ただしルート(たとえば"C \")に限りバックスラッシュを持ちます。 "*"(star)ワイルドカードはディレクトリデリミタの"\"(backslash)もマッチします。(訳注 ちょっと自信ないです)、The "*" (star) wildcard will also match the "\" (backslash) character, so it span s directories. サブディレクトリにあるファイルもまた選択されます。たとえば 「FullPath("c \Windows","*.exe")」というコマンドはWindowsフォルダの中の.exeファイルだけを選択しますが、"Windows\System32"フォルダやWindows以下のすべてのサブフォルダの.exeファイルも処理されます。 この関数はすべてのハードリンク ファイル名を一つのアイテム(二つ名を持ち、同時に違う場所に存在するが、その実体は同じファイル)として扱います。ログファイルには最初に見つかった名前が載ります, so it may appear as if the function has selected some wrong items. この関数はソフトリンク(ジャンクション・シンボリックリンク）を追従しません。 Syntax FullPath(STRING1 , STRING2) Example FileSelect // Select all *.mp3 files in all "music" folders and subfolders. FullPath("*\music","*.mp3") FileActions .... FileEnd // How to include files in a directory but not it s subdirectories. FullPath("c \windows","*") and not (FullPath("c \windows\*","*")) See also FileName DirectoryName DirectoryPath FileSelect FileBoolean FileActions Hidden Select all the items that have the "hidden" attribute set (yes) or not set (no). Hidden items are not included by Windows in an ordinary directory listing. Syntax Hidden(yes) Hidden(no) Example FileSelect # Select all the items that have the "hidden" attribute. Hidden(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions ImportListFromBootOptimize Select the files that are listed in the "%SystemRoot%\Prefetch\Layout.ini" file. Windows XP and Vista create a list of items (files, directories, streams, etc.) that are accessed when the computer boots. MyDefrag can use that list to place the items in a zone. If used in conjunction with the * SortByImportSequence function it will place the items in the order in which they are loaded when booting. * If an item was already placed in a previous zone then it will not be selected and will not be moved. For example, the default Optimize scripts first place the MFT, then the directories, and then the items used when booting. The MFT and the directories are used when booting, but are not moved to the boot optimization zone because they have already been placed in a previous zone. * If you have a multiboot environment then the disk(s) will be optimized for the currently booted Windows. * Boot optimization is not limited to the volume where Windows is installed. If Windows uses items on other volumes, then those other volumes will also be boot optimized. Syntax ImportListFromBootOptimize() Example # Optimize the disks for faster booting. FileSelect ImportListFromBootOptimize() FileActions SortByImportSequence(Ascending) FileEnd Changing the list The "layout.ini" file is a standard Unicode text file and you can look at it with for example the Windows Notepad text editor. Microsoft (and I) feel that booting is finished when the desktop is visible and all programs have been started. The "layout.ini" file therefore lists all items that are used by Windows itself and by the first 32 programs that run after booting. The list is automatically updated by Windows, look at the date/time of the file to see when it was updated last. You can force an update with the following commandline. Rundll32.exe advapi32.dll,ProcessIdleTasks The list can contain some surprising items, files that you were not expecting to be accessed while booting. For example, Windows seems to scan lot s of folders when booting, perhaps it is looking for drivers or DLL s. The folders are listed in the layout.ini file, but the contents of the folders is not. Another example is that many programs contain their icon inside the main executable program. The executable will therefore be listed, not because the program was run when booting but because Windows needed to show the icon on the desktop. The same applies for other kinds of files, for example a big movie may end up in the list because you have a media player that is started in the background that does a quick check to see if the last played file is still there. Other background programs can do similar things. It s possible to change the list in several ways. The easiest way is to use the standard MyDefrag scripting commands. For example, to exclude all files larger than 100 megabytes you can do this # Create zone with files that are used while booting and are smaller than 100Mb. FileSelect ImportListFromBootOptimize() and Size(0,100MB) FileActions SortByImportSequence(Ascending) FileEnd Another way to change the list is by making a copy of the file, editing the file, and then using the MyDefrag * ImportListFromFile fileboolean to import the file. The advantage is that you will get a MyDefrag zone that changes very little. The disadvantage is that you have to do it all over again when something changes on the computer, for example when you install a new driver. See also SortByImportSequence FileSelect FileBoolean FileActions ImportListFromFile Select the items (files, directories) that are listed in the listfile. The STRING is the full path to an item on disk. The listfile is a flat text file, Unicode, UTF-8, or ASCII. The listfile must contain a list of full paths, 1 path per text line. For example C \WINDOWS\SYSTEM32\NTOSKRNL.EXE C \WINDOWS\SYSTEM32\PSHED.DLL C \WINDOWS\SYSTEM32\KDCOM.DLL C \WINDOWS\SYSTEM32\CLFS.SYS Paths that do not exist (or invalid paths) are quietly ignored. Folders are entities by themselves. If the listfile contains the name of a folder then only the folder will be selected, not the items in that folder or subfolders. If the listfile contains the name of an item that has already been processed (placed in a previous zone) then the item will not be selected (ignored). This is a fileboolean function and it only selects items. The FileActions will process the selected items, for example sort by name. The * SortByImportSequence fileaction will order the items in the same sequence in which they are listed in the listfile. Syntax ImportListFromFile(STRING) Example # Select and sort items exactly how I want it. FileSelect ImportListFromFile("c \users\jeroen\MyOptimizeList.txt") FileActions SortByImportSequence(Ascending) FileEnd See also SortByImportSequence FileSelect FileBoolean FileActions ImportListFromProgramHints Select the files that are listed in the "%SystemRoot%\Prefetch\*.pf" files. Windows XP and Vista create a logfile for every program that is started, containing (amongst other things) a list of items (files, directories, streams, etc.) that are accessed during the first 10 seconds of program startup. The logfiles are called "hint" files and are used by the Windows prefetcher to optimize disk access. MyDefrag can analyze the hint files and create a zone that contains all the referenced files. The zone will by default be sorted so that the most used program is first in the zone, with it s files in the order in which they are accessed. The STRING argument specifies which hint file(s) must be imported. Default is all the files in the "%SystemRoot%\Prefetch" folder. You can specify a wildcard "*" to match any character or "?" to match a single character. If the STRING contains a backslash ("\") then it is assumed to be a full path to a folder, to be used instead of the Windows prefetch folder. Hint files older than 30 days are ignored (skipped). The zone is sorted by how often programs have been started, the most started program first. This number is one of the statistics available in the hint files. Please note that a high number of startups does not necessarily mean that a program is important to the user. If a file was already placed in a previous zone then it will not be selected and will not be moved. For example, the default Optimize scripts first place the MFT, then the directories, and then the items used when booting. The MFT and the directories are used when starting a program, but are not moved to the program-hints zone because they have already been placed in a previous zone. The hint files do not list all files that belong to a program. Only the files that are accessed during the first 10 seconds of program startup. Program hints are not limited to the volume where Windows is installed. If a program uses files on other volumes then those other volumes will also be optimized. If you have a multiboot environment then the disk(s) will be optimized for the currently booted Windows. The hint files change a lot. A zone based on these files therefore also changes a lot. Syntax ImportListFromProgramHints(STRING) Example # Optimize the disk for faster program startup. FileSelect ImportListFromProgramHints("*") FileActions SortByImportSequence(Ascending) FileEnd See also SortByImportSequence FileSelect FileBoolean FileActions Largest Select the largests items (size in bytes). The argument is the number of items to be selected. Syntax Largest(NUMBER) Example FileSelect # Select the 10 largest files on the disk. Largest(10) FileActions .... FileEnd See also Smallest FileSelect FileBoolean FileActions LargestFragmentSize Select all the items that have a largest fragment with a size (in bytes) between the minimum (first number) and the maximum (second number). If the second number is zero then the maximum is infinity. Syntax LargestFragmentSize(NUMBER , NUMBER) Example FileSelect # Select all the items that have a largest fragment between 100 and 1000 bytes in size. LargestFragmentSize(100,1000) FileActions .... FileEnd See also FileSelect FileBoolean FileActions LastAccess Select all the items that have a last access time between the minimum time (first parameter) and the maximum time (second parameter). If the first parameter is empty then the minimum time is the beginning of time. If the second parameter is empty then the maximum time is infinity. * See the * LastAccessEnabled fileboolean to test if Windows is configured to record (update) the last access times. * Some improperly programmed utilities cause a change in the last access time of all items on the disk when they scan the disk. Examples are virus scanners, backup programs, text indexers. * On FAT volumes the resolution of the last access time is 1 day. NTFS delays updates to the last access time by up to one hour. Syntax LastAccess(DATETIME , DATETIME) Example FileSelect # Select all the items that were accessed less than 10 days ago. LastAccessEnabled(yes) and LastAccess(10 days ago,now) FileActions .... FileEnd See also LastAccessEnabled FileSelect FileBoolean FileActions LastAccessEnabled Select the items if Windows is configured to record (update) the last access times. This fileboolean is designed to be used together with the * LastAccess fileboolean. Windows XP and Vista have a setting to enable/disable the recording (updating) of the last access times of files. On Vista the default setting is not to record the last access times. You can enable or disable the Windows setting from a commandline with the "fsutil" command See current setting fsutil behavior query disablelastaccess Enable recording of last access time fsutil behavior set disablelastaccess 0 Disable recording of last access time fsutil behavior set disablelastaccess 1 Syntax LastAccessEnabled(yes) LastAccessEnabled(no) Example FileSelect # Select all the items that were accessed less than 10 days ago. LastAccessEnabled(yes) and LastAccess(10 days ago,now) FileActions .... FileEnd See also LastAccess FileSelect FileBoolean FileActions LastChange Select all the items that were changed between the minimum time (first parameter) and the maximum time (second parameter). If the first parameter is empty then the minimum time is the beginning of time. If the second parameter is empty then the maximum time is infinity. * The last-changed date can be older than the creation date, for example when a file was downloaded, or unpacked from an archive (such as zip or arj). Syntax LastChange(DATETIME , DATETIME) Example FileSelect # Select all the items that were changed less than 10 days ago. LastChange(10 days ago,now) FileActions .... FileEnd See also FileSelect FileBoolean FileActions 原文 http //www.mydefrag.com/Scripts-FileBoolean.html 更新日 2010/12/12 (ここで取り扱っている内容の原文をコピーした日付です) NOT Logically negate (invert) a file boolean. If the boolean is true then the result is false, and if the boolean is false then the result is true. Syntax not ( FILEBOOLEAN ) Example FileSelect not ( Name("*.zip") or Name("*.arj") ) FileActions ... FileEnd See also FileSelect FileBoolean FileActions NotToBeIndexed Select all the items that have the "NotToBeIndexed" attribute set (yes) or not set (no). This attribute is used by the Windows content indexing service and indicates that the item is not to be indexed. Syntax NotToBeIndexed(yes) NotToBeIndexed(no) Example FileSelect # Select all the items that have the "NotToBeIndexed" attribute. NotToBeIndexed(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Offline Select all the items that have the "offline" attribute set (yes) or not set (no). This attribute is used by the Windows Remote Storage service and indicates that the file data is physically moved to offline storage. Syntax Offline(yes) Offline(no) Example FileSelect # Select all the items that do not have the "Offline" attribute. Offline(no) FileActions .... FileEnd See also FileSelect FileBoolean FileActions OR Logical OR of two file booleans. The result is true if at least 1 of the booleans is true. Syntax FILEBOOLEAN or FILEBOOLEAN FILEBOOLEAN | FILEBOOLEAN FILEBOOLEAN || FILEBOOLEAN Example FileSelect Size(10000000,0) or LastAccess("","1 month ago") FileActions ... FileEnd See also FileSelect FileBoolean FileActions Readonly Select all the items that are read-only (yes) or not read-only (no). Syntax Readonly(yes) Readonly(no) Example FileSelect # Select all the items that are read-only. Readonly(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions SelectNtfsSystemFiles Select all the NTFS system files. These files are usually not visible, but they exist on all NTFS disks. The function selects all the files that are in the root directory of the volume and have a name that begins with "$" (dollar sign), except for "$RECYCLE.BIN", and all files in the $Extend folder and it s subfolders. * This function is intended to be used together with the * PlaceNtfsSystemFiles fileaction. Inode Filename Description 0 $MFT Master File Table - An index of every file. 1 $MFTMirr A backup copy of the first 4 records of the MFT. 2 $LogFile Transactional logging file. 3 $Volume Serial number, creation time, dirty flag. 4 $AttrDef Attribute definitions. 6 $Bitmap Contains volume s cluster map (in-use vs. free). 7 $Boot Boot record of the volume. 8 $BadClus Lists bad clusters on the volume. 9 $Quota [Windows NT only] Quota information. 9 $Secure Security descriptors used by the volume. 10 $UpCase Table of uppercase characters used for collating. 11 $Extend A directory for $ObjId, $Quota, $Reparse, $UsnJrnl. $Extend\$ObjId Unique Ids given to every file. $Extend\$Quota Quota information. $Extend\$Reparse Reparse point information. $Extend\$UsnJrnl USN Journal. $Extend\$RmMetadata Transactional data. Syntax SelectNtfsSystemFiles(yes) SelectNtfsSystemFiles(no) Example FileSelect # Select all the NTFS system files. SelectNtfsSystemFiles(yes) FileActions # Place the selected files, sorted by their full path. PlaceNtfsSystemFiles(Ascending,MftSize * 0.1) FileEnd See also PlaceNtfsSystemFiles ReclaimNtfsReservedAreas Size Select all the items that have a size in bytes between the minimum (first number) and maximum (second number). If the second number is zero then the maximum is infinity. * Sparse files can have a larger size than what they are actually using on the disk. Syntax Size(NUMBER , NUMBER) Example FileSelect # Select all files with a size up to 10 gigabyte. Size(0,10000000000) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Smallest Select the smallest items (size in bytes). The argument is the number of items to be selected. Syntax Smallest(NUMBER) Example FileSelect # Select the 10 smallest files on the disk. Smallest(10) FileActions .... FileEnd See also Largest FileSelect FileBoolean FileActions SmallestFragmentSize Select all the items that have a smallest fragment with a size (in bytes) between the minimum (first number) and the maximum (second number). If the second number is zero then the maximum is infinity. Syntax SmallestFragmentSize(NUMBER , NUMBER) Example FileSelect # Select all the items that have a smallest fragment between 100 and 1000 bytes in size. SmallestFragmentSize(100,1000) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Sparse Select all the items that are sparse (yes) or not sparse (no). Syntax Sparse(yes) Sparse(no) Example FileSelect # Select all the items that are sparse. Sparse(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions System Select all the items that have the "system" attribute set (yes) or not set (no). This attribute is used by Windows to indicate items that are part of Windows, or that are used exclusively by Windows. This definition includes files such as the pagefile, "desktop.ini" files, just about everything in the Windows folder (including infrequently used stuff), temporary files, files in the recycle bin, and lot s of other stuff. Syntax System(yes) System(no) Example FileSelect # Select all the items that have the "System" attribute. System(yes) FileActions .... FileEnd Tip You can get a list of all the system files on the C disk with the following Windows commandline dir /A S /S c See also FileSelect FileBoolean FileActions Temporary Select all the items that have the "temporary" attribute set (yes) or not set (no). This attribute is used by Windows to indicate temporary items. The file system will attempt to keep all of the data in memory for quick access, rather than flushing it back to mass storage. Syntax Temporary(yes) Temporary(no) Example FileSelect # Select all the items that have the "Temporary" attribute. Temporary(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Unmovable Select all the items that MyDefrag could not move. MyDefrag initially assumes that all items on disk are movable. Only after the Windows defragmentation API has refused to move an item will an item be "unmovable". Syntax Unmovable(yes) Unmovable(no) Example FileSelect # Select all the items that have the "Unmovable" attribute. Unmovable(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions Virtual Select all the items that have the "virtual" attribute set (yes) or not set (no). Syntax Virtual(yes) Virtual(no) Example FileSelect # Select all the items that have the "Virtual" attribute. Virtual(yes) FileActions .... FileEnd See also FileSelect FileBoolean FileActions
https://w.atwiki.jp/touhoukashi/pages/5026.html
【登録タグ D めらみぽっぷ 凋叶棕 曲 東方幻奏響UROBOROS弐 ～fAIRYtAILoVERdRIVE～ 禁じざるをえない遊戯】 【注意】 現在、このページはJavaScriptの利用が一時制限されています。この表示状態ではトラック情報が正しく表示されません。 この問題は、以下のいずれかが原因となっています。 ページがAMP表示となっている ウィキ内検索からページを表示している これを解決するには、こちらをクリックし、ページを通常表示にしてください。 /** General styling **/ @font-face { font-family Noto Sans JP ; font-display swap; font-style normal; font-weight 350; src url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/10/NotoSansCJKjp-DemiLight.woff2) format( woff2 ), url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/9/NotoSansCJKjp-DemiLight.woff) format( woff ), url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/8/NotoSansCJKjp-DemiLight.ttf) format( truetype ); } @font-face { font-family Noto Sans JP ; font-display swap; font-style normal; font-weight bold; src url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/13/NotoSansCJKjp-Medium.woff2) format( woff2 ), url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/12/NotoSansCJKjp-Medium.woff) format( woff ), url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2972/11/NotoSansCJKjp-Medium.ttf) format( truetype ); } rt { font-family Arial, Verdana, Helvetica, sans-serif; } /** Main table styling **/ #trackinfo, #lyrics { font-family Noto Sans JP , sans-serif; font-weight 350; } .track_number { font-family Rockwell; font-weight bold; } .track_number after { content . ; } #track_args, .amp_text { display none; } #trackinfo { position relative; float right; margin 0 0 1em 1em; padding 0.3em; width 320px; border-collapse separate; border-radius 5px; border-spacing 0; background-color #F9F9F9; font-size 90%; line-height 1.4em; } #trackinfo th { white-space nowrap; } #trackinfo th, #trackinfo td { border none !important; } #trackinfo thead th { background-color #D8D8D8; box-shadow 0 -3px #F9F9F9 inset; padding 4px 2.5em 7px; white-space normal; font-size 120%; text-align center; } .trackrow { background-color #F0F0F0; box-shadow 0 2px #F9F9F9 inset, 0 -2px #F9F9F9 inset; } #trackinfo td ul { margin 0; padding 0; list-style none; } #trackinfo li { line-height 16px; } #trackinfo li nth-of-type(n+2) { margin-top 6px; } #trackinfo dl { margin 0; } #trackinfo dt { font-size small; font-weight bold; } #trackinfo dd { margin-left 1.2em; } #trackinfo dd + dt { margin-top .5em; } #trackinfo_help { position absolute; top 3px; right 8px; font-size 80%; } /** Media styling **/ #trackinfo .media th { background-color #D8D8D8; padding 4px 0; font-size 95%; text-align center; } .media td { padding 0 2px; } .media iframe nth-of-type(n+2) { margin-top 0.3em; } .youtube + .nicovideo, .youtube + .soundcloud, .nicovideo + .soundcloud { margin-top 0.75em; } .media_section { display flex; align-items center; text-align center; } .media_section before, .media_section after { display block; flex-grow 1; content ; height 1px; } .media_section before { margin-right 0.5em; background linear-gradient(-90deg, #888, transparent); } .media_section after { margin-left 0.5em; background linear-gradient(90deg, #888, transparent); } .media_notice { color firebrick; font-size 77.5%; } /** Around track styling **/ .next-track { float right; } /** Infomation styling **/ #trackinfo .info_header th { padding .3em .5em; background-color #D8D8D8; font-size 95%; } #trackinfo .infomation_show_btn_wrapper { float right; font-size 12px; user-select none; } #trackinfo .infomation_show_btn { cursor pointer; } #trackinfo .info_content td { padding 0 0 0 5px; height 0; transition .3s; } #trackinfo .info_content ul { padding 0; margin 0; max-height 0; list-style initial; transition .3s; } #trackinfo .info_content li { opacity 0; visibility hidden; margin 0 0 0 1.5em; transition .3s, opacity .2s; } #trackinfo .info_content.infomation_show td { padding 5px; height 100%; } #trackinfo .info_content.infomation_show ul { padding 5px 0; max-height 50em; } #trackinfo .info_content.infomation_show li { opacity 1; visibility visible; } #trackinfo .info_content.infomation_show li nth-of-type(n+2) { margin-top 10px; } /** Lyrics styling **/ #lyrics { font-size 1.06em; line-height 1.6em; } .not_in_card, .inaudible { display inline; position relative; } .not_in_card { border-bottom dashed 1px #D0D0D0; } .tooltip { display flex; visibility hidden; position absolute; top -42.5px; left 0; width 275px; min-height 20px; max-height 100px; padding 10px; border-radius 5px; background-color #555; align-items center; color #FFF; font-size 85%; line-height 20px; text-align center; white-space nowrap; opacity 0; transition 0.7s; -webkit-user-select none; -moz-user-select none; -ms-user-select none; user-select none; } .inaudible .tooltip { top -68.5px; } span hover + .tooltip { visibility visible; top -47.5px; opacity 0.8; transition 0.3s; } .inaudible span hover + .tooltip { top -73.5px; } .not_in_card span.hide { top -42.5px; opacity 0; transition 0.7s; } .inaudible .img { display inline-block; width 3.45em; height 1.25em; margin-right 4px; margin-bottom -3.5px; margin-left 4px; background-image url(https //img.atwikiimg.com/www31.atwiki.jp/touhoukashi/attach/2971/7/Inaudible.png); background-size contain; background-repeat no-repeat; } .not_in_card after, .inaudible .img after { content ; visibility hidden; position absolute; top -8.5px; left 42.5%; border-width 5px; border-style solid; border-color #555 transparent transparent transparent; opacity 0; transition 0.7s; } .not_in_card hover after, .inaudible .img hover after { content ; visibility visible; top -13.5px; left 42.5%; opacity 0.8; transition 0.3s; } .not_in_card after { top -2.5px; left 50%; } .not_in_card hover after { top -7.5px; left 50%; } .not_in_card.hide after { visibility hidden; top -2.5px; opacity 0; transition 0.7s; } /** For mobile device styling **/ .uk-overflow-container { display inline; } #trackinfo.mobile { display table; float none; width 100%; margin auto; margin-bottom 1em; } #trackinfo.mobile th { text-transform none; } #trackinfo.mobile tbody tr not(.media) th { text-align left; background-color unset; } #trackinfo.mobile td { white-space normal; } document.addEventListener( DOMContentLoaded , function() { use strict ; const headers = { title アルバム別曲名 , album アルバム , circle サークル , vocal Vocal , lyric Lyric , chorus Chorus , narrator Narration , rap Rap , voice Voice , whistle Whistle (口笛) , translate Translation (翻訳) , arrange Arrange , artist Artist , bass Bass , cajon Cajon (カホン) , drum Drum , guitar Guitar , keyboard Keyboard , mc MC , mix Mix , piano Piano , sax Sax , strings Strings , synthesizer Synthesizer , trumpet Trumpet , violin Violin , original 原曲 , image_song イメージ曲 }; const rPagename = /(?=^|.*
https://w.atwiki.jp/mainichi-matome/pages/1976.html
Craracked.com The 8 Most Terrifying Restaurants from Around the World世界中で最も恐ろしい、ゾッとするような８つのレストラン #8.Guo-Li-Zhuang A Penis Buffet第八位 Guo-Li-Zhuang という名のペニスビュッフェ #7.Cannibalistic Sushi第七位 食人寿司 #6.Dinner In The Sky第六位 空中での食事 #4.Modern Toilet第四位 近代的なトイレ #3. Eternity第三位 Eternity(永遠) #2. Fortezza Medicea第二位 メディチ要塞 #1.“Roppongi”第一位 「六本木」 ソースロンダリングの経路#7.Cannibalistic Sushi の経路 #1.“Roppongi” の経路 関連ページ Craracked.com http //www.cracked.com/ America s Only Humor Video Site, Since 1958 検討：世界のニュースの中に毎日を紛れ込ませるとどうなるかでも述べているように、事実のなかに嘘を紛れ込ませると、嘘も事実に見えてくることがあります。 これは大変恐ろしいことです。 The 8 Most Terrifying Restaurants from Around the World 世界中で最も恐ろしい、ゾッとするような８つのレストラン http //www.cracked.com/blog/2008/09/11/9-restaurants-designed-to-ruin-your-appetite/ 「世界の８つの恐ろしいレストラン」の1位に「六本木の…」があります。 この８つのレストランの中には、空中ワイヤー釣りレストランや刑務所レストランのように実在するものも取り上げられています。 The 8 Most Terrifying Restaurants from Around the World by Michael Swaim 世界中で最も恐ろしい、ゾッとするような８つのレストラン For centuries, restaurants have been making the same fiscal error time and time again serving delicious food at reasonable prices. Truly a recipe for fiduciary disaster. 何世紀にも渡って、レストランは同じような財政上の間違いを幾度となく犯してきました。手ごろなお値段で美味しい食べ物を提供してきたのです。 本当に、信託災難のレシピです。 Here at least are eight restaurants that understand, to truly make a profit in the food business, you want to guarantee your patrons eat as little as possible, then get the hell out. It’s called “high turnover.” Ask an economist. フードビジネスで本当に利益を上げるには、できるだけ食べない、そして急いで立ち去る常連客のご贔屓が必要だと理解している少なくとも八軒のレストランがここにあります。 『高回転率』と呼ばれています。 経済学者に尋ねてみなさい。 #8.Guo-Li-Zhuang A Penis Buffet 第八位 Guo-Li-Zhuang という名のペニスビュッフェ Are you suffering from a low sex drive? Lack confidence and virility? Love stuffing animal penises into your mouth? あなたは性欲低下に悩んでいますか？ 自信と精力が不足していますか？ 動物の陰茎を、是非にも口に含みたいですか？ If you answered “yes” to any of the above questions, Guo-Li-Zhuang may just be the lunch spot for you. Or you may just be a pervert. もしあなたが上記の質問のどれかに「はい」と答えたなら、Guo-Li-Zhuangは絶好のランチスポットになるでしょう。 もしくは、あなたが単に性倒錯者であるなら。 Assuming the former, you’ll get a blast and a half out of Guo-Li-Zhuang’s tasteful interior decoration, soothing ambient music, and kitchen full of cooked animal members. 前者だと仮定すると、あなたはGuo-Li-Zhuangの趣味のいい室内装飾に興奮に興奮を重ねるでしょう。うっとりさせる店内音楽が流れ、そして厨房は調理された動物の体の一部でいっぱいです。 And when it comes to man-meat, Guo-Li-Zhuang just can’t be beat! They’ve got horse penis, goat penis, dog penis, pig penis, cock cock…why, they’ve got more penis than you can shake your dick at! (Dick shaking not recommended, as you risk losing your penis to another hungry customer). ちんちんということになると、Guo-Li-Zhuangは本当に最高です！ 馬のペニス、ヤギのペニス、犬のペニス、豚のペニス、雄鶏のちんちん…なぜ、彼らはあなたが ちんちんを振って指して数えることができる以上のちんちんを扱うのでしょう！ （ちんちんを振って指すのはお勧めしません。腹を空かせた他の客に食べられてしまう恐れがありますから。） All that and balls to boot! At Guo-Li-Zhuang, you can get any dick with testicles on the side; the way God intended. Would you like pig balls with a goat dick? Done. そういったものから、おまけに睾丸にいたるまで！ Guo-Li-Zhuangではあなたは、神が意図して創られた形のままの、いかなる ちんちんも、睾丸を添えて頂けますよ。 豚の睾丸の、ヤギのちんちん添えですね？かしこまりました。 Dog penis with one horse ball and one rooster ball? Why the hell not? A big horse cock and two tiny chicken balls? Hilarious! 馬とオンドリの睾丸が添えられた犬のペニスはどう？ は？それは嫌いなの？ じゃあ、でかい馬のちんちんと二つの小さな鶏の睾丸はどう？ 爆笑！ Or why not indulge yourself with the “man’s mighty meal,” a plate of three floppy dicks and eight？count‘em eight!？swollen testicles, guaranteed to give you back your virility or send you screaming into the streets. というか、何故「男性用のすんごい食事」に耽溺しないのですか？三本の柔らかなちんちんと、八個の、いいですか、数えてください。八個の！膨れあがった睾丸との盛り合わせ、この料理はあなたに精力を取り戻させてくれて、ひゃっほお！と快哉を挙げながら街に繰り出させてくれること間違いなしですよ。 Guo-Li-Zhuang? More like Chow-On-Wang! Ordering sausage and eggs for breakfast just got a little more interesting. Guo-Li-Zhuang?それよりも、”ちんちん-を-食べる”って店名の方がそれっぽいじゃん! （西洋人がよく朝食に食べている）ソーセージと卵をこのレストランでオーダーしたら、（ちんちんとタマタマだらけの メニューなわけだから、）ちょっと面白い経験が出来ますよ。 #7.Cannibalistic Sushi 第七位 食人寿司 For many Americans, eating rolls of raw fish can be a tough sell. 多くのアメリカ人にとって、生魚の巻き物を食べることは受け入れ難いことであるかもしれません。 But if you’re one of the thousands of open-minded Yanks who’ve fallen under the spell of sushi in recent years, then what better way to totally ruin it for yourself than eating it out of a dead person? しかし、もしあなたが、寿司の魅力のとりこになる、生魚に偏見の無い近年の数千人のアメリカ人の内の一人だったなら、死んだ人間を材料にして作られたものを食べる以上にあなた自身を完全に零落させる方法があるでしょうか。 At Cannibalistic Sushi, an edible body is wheeled out to your family on a gurney, along with as much scotch as you need to disinfect your forks and convince yourself that this was a good idea. 食人寿司では、食用の死体がストレッチャーに載せられてあなたの家族の前に運ばれてきます。フォークを消毒するために、そして、これはいい考えなんだと自分自身を納得させるためにあなたが必要とするだけの分量のスコッチと一緒に。 Then, it’s time to dig in! Whether you’re using chopsticks, a knife and fork, or your bare hands, one thing’s for certain you’ll be feasting on the entrails of a human being. さあ、かぶりつく時間だぞ！ 箸を使おうが、ナイフとフォークを使おうが、手づかみだろうが、1つだけ確かなことがある。あなたは人の内臓のごちそうを食べるだろうことです。 The artisans at Cannibalistic Sushi have taken pains to ensure that the human body you are ripping into is as lifelike as possible. 食人寿司の職人は、あなたが食い付いている人体が、確実にできるだけ実物そくりになるようにするために苦心しています。 The sushi inside is shaped to resemble human organs, a red “blood sauce” is embedded in the skin layer so as to create realistic bleeding, and your corpse even has a set of papier mache genitals! It’s like your third grade arts and crafts project all over again. この寿司の内部は、人間の内臓に酷似するようにつくられます。そしてその皮膚の表面薄層には、赤い「血液ソース」が、現実的な出血を引き起こすために、埋め込まれています。そして、あなたに提供された死体には、ひととおりの張り子の性器がありさえします! それは、あなたの小学3年生の図工の時間の再演のようです。 If you’re an experienced cannibal, make sure to specify a male or female corpse when ordering, and show the other diners just how sophisticated your taste in human flesh is. あなたが経験豊富な人食い人種であるなら、死体を注文するときには、男性のものか女性のものかを忘れずに指定して、あなたの人肉の趣味がいったいどれくらい洗練されているのかを他の客に示してください。 And although eating at Cannibalistic Sushi may not quell the voices in your head that command you to kill and devour those around you, it will certainly shut them up for a day or two. ああ、食人寿司で食事する程度では、あなたの頭の中の、あなたの周りの（人間）を殺して、むさぼり食えと命令する声は静まらないかもしれませんが、ここで食事することは確かに1日か2日間は、その声を止めてくれるでしょう。 Confuse your inner psychopath by making a reservation at Cannibalistic Sushi today! 食人寿司を予約することによって、あなたの内なる狂人をごまかしてください！ #6.Dinner In The Sky 第六位 空中での食事 Not a restaurant in the true sense, Dinner In The Sky is more of a philosophy. The philosophy that if food tastes better outdoors, then it will taste even better than that suspended thirteen stories in the air. 言葉の真の意味においてのレストランではなく、Dinner In The Sky はむしろ哲学です。 食物は屋外でより美味しいのだとする哲学なら、ひいては空中１３階に吊り下げられてのそれは、それよりさらに一層美味しいでしょう。 By making a reservation, you can guarantee you and up to 21 guests the dining experience of an extremely bizarre lifetime. At the appointed date, a Belgian crane will come and hoist your table, seats, waiters and even an entertainer into the air for a two-hour meal. The food is exceptional, and the entertainment consists of a man on all fours clutching at the ground and weeping until you are once again lowered. 予約を入れることによって、あなたはあなたと最大２１人までのゲストに極端に奇抜な、生涯にまたとない食事の経験を保証できます。 約束の日付に、ベルギーのクレーンが来てあなたのテーブル、座席、ウエイターそしてエンターテイナーまでもを、二時間の食事のために高く吊り上げるでしょう。 食事は秀逸で、そしてエンターテイメントは、あなたが再度下げられるまで四つんばいになって地べたを掴もうとしてシクシク泣いている男性から成り立ちます。 With Dinner In The Sky, you will truly experience all the labia-clenching terror that height has to offer. Your seats are groundless, leaving your legs dangling in the breeze, a testament to man’s refusal to not do crazy things that affront God. You are harnessed in however, so diners should be sure to evacuate their bowels before boarding, or else risk giving someone below the worst day of their lives. Dinner In The Skyでは、あなたは本当に、高さが提供せざるを得ない全ての唇を引き結ぶ恐怖を体験するでしょう。 あなたの座席は根も葉もなく、あなたの脚をそよ風の中に踊らせたままにしておきます、 神様を侮辱する正気でない振る舞いをしないという、人間の辞退の証です。 あなたはハーネスを着けられてはいますが、なので食事客は必ず搭乗前に彼らの腸を空にしなければなりません。さもなくば、リスクが誰かに、彼らの人生最悪の日よりも悪いものを与えるでしょう。 At 130 feet in the air, depending on your location, you can expect wind, fog, rain, and low flying birds to add a healthy sense of atmos-fear to your meal. And if by chance a romantic thunderstorm should swell, rest assured that you are fastened to a 130 foot-tall metal rod. 空中１３０フィートのところで、あなたの所在地次第で、あなたは風、霧、雨、そして健康的な「大気」(*1)の感覚をあなたの食事に加えるために低く飛ぶ鳥たちを期待できます。 そしてもし偶然にもロマンティックな激しい雷雨がうねることがあったなら、１３０フィートの高さの金属の棒に縛りつけられての休憩が保証されます。 #4.Modern Toilet 第四位 近代的なトイレ If you’re still eating at Old Fashioned Toilet, you’re woefully behind the times, and let’s not even discuss Chamber Pot and The Outhouse. The fact is, today’s modern world demands a modern toilet?for sitting on while eating, for eating out of, for…actually that’s all the toilet uses we can really remember. もし貴方がいまだに旧式トイレで食事しているのなら、あなたは痛ましいほどに時代に遅れなので、尿瓶と屋外トイレについて議論することさえやめておきましょう。 実際は、現今の現代世界は、近代的なトイレを要求しているんですよ？食べている間に座るために、そこから取って食べるために、それと…実のところは、それは私たちが実際に思い出すことができる、そのトイレの用途の全てです。 Thank heavens, then, that the Modern Toilet restaurant has seen fit to outfit their restaurant with only the most modern plastic lids, fuzzy seat covers, and fine ceramic bowls, and then filled those bowls with a hot steaming pile of soup. And all Modern Toilet restaurants are co-ed, so don’t fret; your hubby won’t miss watching you guzzle soup out of a urinal, head held low while drops of broth splatter onto your face. あーよかった、それなら、そのモダン・トイレ・レストランは、彼らのレストランに、最もモダンなプラスティック製の蓋、微毛のある便座カバー、そして素晴らしいセラミック製の便器のみを取り付けて、そしてその次にはそれらの便器を湯気が出るほど熱いなみなみのスープで満たすのに向いています。 そして、全てのモダン・トイレ・レストランは男女共用なので、あなたの夫が、あなたが尿瓶からスープをガブガブ飲み、ブロスの滴があなたの顔にはね散るのにもかかわらず、頭を低く持って行くのを見逃そうとしなくても、イライラしないで下さい。 And if the thought of eating a soup of yellow broth and chunks of cooked beef out of a toiled bowl seems less than appetizing to you, not to worry! Simply drop the soup into the toilet that is your seat, and flush it away. そして、黄色いブロスのスープと 調理された牛肉の大きな塊を便器から取り出して食べるという考えが、決してあなたの食欲をそそりはしないように思えたとしても、ご心配には及びません！ 単に、あなたの座席であるトイレにスープを放り込むと、それを水で洗い流してしまいますから。 Of course, the toilets aren’t functional, and a waiter will be along shortly to escort you off the premises. But at least you didn’t have to eat the shit soup! Instead, you can skip straight to dessert, a heaping helping of chocolate soft serve, fresh out of the bowl. もちろん、そのトイレは 機能するものではありませんし、ウエイターはすぐさま、あなたを部屋の外へエスコートするために来るでしょう。 しかし少なくとも、あなたは大便スープを食べずとも済んだのです！ 代わりに、あなたは、品目を飛ばして、便器に絞られた山盛りのチョコレートソフトクリーム一盛りのデザートに進むことができます。 So go out and spread the word about Modern Toilet, if only because you don’t want a confused mall patron running in and pissing into your Chicken Curry. 出かけて、モダントイレに関する噂を広めなさい。混乱したショッピングセンターのパトロンが駆け込んできて、あなたのチキンカレーに小便して欲しくだけはないのなら。 #3. Eternity 第三位 Eternity(永遠) If you’re anything like us Cracked writers, you can’t count the number of times you tried to cheer up a friend after a death in their family by surprising them with a trip to Chuck E. Cheese’s. And no matter how many times they run out of the building screaming, it never stops being funny. もしあなたが、私たちのような頭のおかしいライターに似ているところがあるなら、チャッキーチーズへの旅行によって驚かせて、家族を急に喪った友人を励まそうとした回数は数えられないほどでしょうし、そこで友人が何度 泣き叫びながらビルから走り出ても、旅行が愉快なことは決して変わりはしないでしょう。 Luckily, most will forgive you if you present them with an eighty-ticket unbreakable comb you won playing skee-ball. 幸いなことに、あなたがチャッキーチーズのスキーボールで獲得したポケットコーム（チケット８０枚相当分の景品です）をプレゼントしたら、彼らのほとんどはあなたを許すでしょう。 But if you’re not like us Cracked writers, you may want to mourn their recent loss at a place more befitting the occasion. しかしもし貴方が、私たちのような頭のおかしいライターではないのなら、あなたはおそらく、もっとその出来事に相応しい場所で、彼らに降りかかったばかりの喪失を悼みたいことでしょう。 Enter Eternity, the restaurant designed for people who have lost a loved one, and don’t want to move on any time soon. Eternityに入ると、このレストランは愛する人を亡くして、今すぐには気持ちを切り替えたくはない人々向けにデザインされています。 The windowless, coffin-shaped cafe is also an ideal dining destination for those who would like to recall the dead, but live far from a cemetery and find their remembrances go well with a banana nut muffin, not to mention goth kids and weird loners. 窓の無い、棺の形をしたカフェは、死者を思い出したいのだけれど、墓地から遠いところに住み、 バナナナッツマフィンが回想を順調にさせると気づいた人向けの理想の食事目的地でもあります。野蛮なガキどもや孤独好きな奇人向けであることは言うまでもなく。 The restaurant features funeral wreaths, white lilies on each table, and walls made of what appears to be black plastic, in case you happened to bury your mother in a garbage bag. このレストランは葬儀用の花輪、各テーブルに活けてある白百合、そして黒いプラスチックで出来ているように思われる壁、を呼び物にしています。あなたが母親をゴミ袋に埋葬するはめになるといけないので。 Although if that’s the case, we’ve got some grisly news for you involving wolves and dismemberment. もしゴミ袋に埋葬する気なのだとしたらですが、私たちは泥棒と切断に関するいくつかの身の毛もよだつような情報を所持しています。 In fact, you might want to sit down for this. Banana nut muffin? 実のところ、あなたはこれのために座りたいのかもしれない。バナナナッツマフィン？ #2. Fortezza Medicea 第二位 メディチ要塞 This exclusive restaurant in Voltera, Italy has tables booked weeks in advance. In order to secure a table, you and your guests will need to call ahead, submit to full background checks, and, once on premises, the maitre d’ and his helpful staff will frisk you and take your cell phones and anything else they deem a risk. このイタリアはボルテラ(*2)にある高級レストランは、テーブルを何週間も前に予約されます。 テーブルを確保するためには、あなたとあなたの招待客は事前に電話する必要があるでしょう、完全な身元調査を提出し、そして、一度 店に来たなら、支配人とその有能なスタッフがあなたのボディーチェックをし、あなたの携帯電話と、その他の彼らが危険だと考えたものを取り上げるでしょう。 Why the precautions? Is it because their chicken parmesan is so delicious, patrons have been known to storm the kitchen, threatening the life of the cook staff lest they reveal what Hell-demon they blew to get the recipe? Yes, but also because Fortezza Medicea is a maximum security prison. その予防措置は何のためなのか？ 彼らのチキン・パルメザンがとても美味で、常連客は台所を攻撃することで知られていて、調理スタッフの人生を脅かしていて、レシピを手にするために地獄の悪魔が襲撃するといけないからだということを彼らが明かしたからなのでしょうか？ ええ、何故ならFortezza Mediceaはまた、最高レベルのセキュリティーの監獄でもあるからです。 Not only is it a prison, but the wait staff and cook staff are all convicted inmates. The head chef is doing life for murder, as is the piano player Bruno (Bruno will take no requests. Do not speak to or make eye contact with Bruno). The cooking is accomplished entirely with plastic utensils, for the safety of the customers, and added “casual” feel of the establishment. Why, dining at Fortezze Medicea is just like having a picnic! A picnic with the mafia! そこは監獄であるだけではなく、給仕スタッフと調理スタップは全員が有罪判決を受けた囚人です。 料理長は殺人による終身刑に服している、ピアノ演奏者のブルーノです。 （ブルーノはリクエストを受け付けはしないでしょう。 決してブルーノとしゃべったり、目線を合わせたりしないように） 調理は完全にプラスチックの器具で行われます、顧客の安全のために、そして施設の雰囲気に「カジュアルさ」を加味するために。 なぜ、Fortezze Mediceaでの食事はまるでピクニックに出かけているかのようなのでしょう！ マフィアと一緒のピクニック！ But not to worry; while you eat, you will at all times be under the hawk-like gaze of 20 prison warders, just waiting for an inevitable violent escape attempt. Will you be taken hostage at (plastic) knife-point, used as a human shield by a convict, or simply gunned down in the cross fire? It all adds to the deliciousness of their signature red wine sauce. けれど心配無用です。あなたが食べている間、あなたは常に不可避である暴力による脱走の企てをただ待っている２０名の看守の、鷹のごとき注視の元にあります。 あなたは(プラスチックの)ナイフの刃先で人質に取られ、人間の盾として囚人に利用される、つまり容易く十字砲火の凶弾に倒れる気はありませんか? それはすべて、彼らの特製赤ワインソースの美味しさを増幅させます。 Shanks, Fortezza Medicea, for proving that even killers-for-hire can make an alfredo sauce that’s to die for! ありがとう(*3)、雇われ殺人者であっても、死ぬほど食べたいアルフレイドウ・ソース(*4)を作れるのだと証明するためのFortezza Medicea！ #1.“Roppongi” 第一位 「六本木」 The last restaurant on our list is so exclusive, it doesn’t even have a name. 私たちのリストに載っている最後のレストランは、本当に排他的で、名前さえありません。 To eat there costs between two to eight thousand dollars, and you must be a member (to qualify as a member, you must have a yearly income in excess of $175,000…well, in Yen). ここで食事するためには、2000から8000ドルかかりますし、それにあなたは会員にもならなくてはなりません。 （会員としての資格を得るには、年収が175000ドル以上なければいけません…もちろん、円でね） It’s a secretive, controversial club located underground in Tokyo’s fashionable Roppongi District. Where you have sex with your food. 東京の洒落た六本木地区の地下に居を構えている秘密の、論議を巻き起こすクラブです。 食べ物とセックスする場所です。 Playing with your food has never been taken so literally. At the Roppongi club, you’ll get to make love to your choice of a chicken, dog, pig, or goat; male or female. At this point, unless you’ve overstepped your bounds, the animal is still alive, and presumably frisky. 食べ物で本当に おイタをしたことなんて、絶対に経験ないでしょう。 しかし六本木クラブでは、あなたが選んだ鶏や犬、豚、ヤギとセックスできるでしょう。オスとでもメスとでもね。 この時点では、あなたが節度を守れば、動物はまだ生きていて、おそらく元気に跳ね回っているでしょう。 Once the deed is done, you (and your family? Guests? We’re not really sure what you want to do here) retire to the dining area. 一旦、行為をしたら、あなたは(あなたの家族と一緒にでしょうか?あなたの招待客と一緒にでしょうか? 私たちはあなたがここで何をしたいのかが全く解りませんが) 食事場所に退いてください。 In a matter of minutes, you are presented with a delicious meal of roasted whatever-animal-you-just-fucked. The restaurant is not forthcoming with many details, but one imagines, largely for the sake of one’s sanity, that the animal is cleaned out first. ものの数分で、あなたは≪あなたがファックしたばかりの動物の≫、美味な炙り肉を相伴できるでしょう。 このレストランは詳細の多くを公表されていませんが、しかしほとんど私の正気のために私が推測するところでは、その動物は先に一掃されるのでしょう。 Admittedly, this exclusive dining establishment is not for everyone, but if you’re a rich person who has literally exhausted every other human experience (remember, that includes injecting heroin into your eyeball), then why not top off your life of debauchery with a humped dog? ご指摘の通り、富裕層向けのディナーは万人向けに設立されたものではありません。しかしもしあなたが、ありとあらゆる体験（体験の中には、眼球にヘロインを注入することも含まれることを覚えておいてくれ）に完全に食傷した裕福な人間なら、ヤられた犬で道楽人生を締めくくられてはいかがでしょう？ As one of the patrons (who wished to remain anonymous) stated, “the appeal of the place just came about because when people have got money and done everything else, they turn towards bestiality.” 常連客の一人（匿名希望）は述べます。「人は金を持って、あらゆる事をやりつくすと、獣姦に走るからここは魅力的なのさ」 We’re on to you, Bill Gates, Donald Trump, J.K. Rowling and Paul McCartney. Watch it. 私たちはあなたのやってることをお見通しですよ、ビル・ゲイツ、ドナルド・トランプ、J.K.ローリング、およびポール・マッカートニー。気をつけて。 ソースロンダリングの経路 #7.Cannibalistic Sushi の経路 (2006/11/08) Weird Asia News "Japanese Banquet of Cannibalism" http //www.weirdasianews.com/2006/11/08/japanese-banquet-of-cannibalism/ ↓ (2007/09/04) Pork Your Pork "Feast Like a Cannibal at the Human Banquet" http //porkyourpork.bestuncensored.com/feast-like-a-cannibal-at-the-human-banquet ↓ (2008/09/11) CRACKED.COM "The 8 Most Terrifying Restaurants from Around the World" - #7. Cannibalistic Sushi http //www.cracked.com/blog/2008/09/11/9-restaurants-designed-to-ruin-your-appetite/ #1.“Roppongi” の経路 実話GON!ナックルズ2007年9月25日号 P60-63 「エロバカ都市伝説」 ↓ (2007/09/17) Mainichi News "The Cook, the Beast, the Vice and its Lover" ↓ (2007/09/17) InventorSpot "New Restaurant Lets you Pork your Pork" http //inventorspot.com/articles/pork_your_pork_6934 http //porkyourpork.bestuncensored.com/pork-your-pork (ここにリダイレクトされている) ↓ (2008/09/11) CRACKED.COM "The 8 Most Terrifying Restaurants from Around the World" - #1. "Roppongi” http //www.cracked.com/blog/2008/09/11/9-restaurants-designed-to-ruin-your-appetite/ 関連ページ The Cook, the Beast, the Vice and its Lover WaiWaiの記事を転載した英語サイト：C
https://w.atwiki.jp/reisiki/pages/87.html
# Doxyfile 1.5.8 # This file describes the settings to be used by the documentation system# doxygen (www.doxygen.org) for a project## All text after a hash (#) is considered a comment and will be ignored# The format is # TAG = value [value, ...]# For lists items can also be appended using # TAG += value [value, ...]# Values that contain spaces should be placed between quotes (" ") #---------------------------------------------------------------------------# Project related configuration options#--------------------------------------------------------------------------- # This tag specifies the encoding used for all characters in the config file # that follow. The default is UTF-8 which is also the encoding used for all # text before the first occurrence of this tag. Doxygen uses libiconv (or the # iconv built into libc) for the transcoding. See # http //www.gnu.org/software/libiconv for the list of possible encodings. DOXYFILE_ENCODING = UTF-8 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded # by quotes) that should identify the project. PROJECT_NAME = siki # The PROJECT_NUMBER tag can be used to enter a project or revision number. # This could be handy for archiving the generated documentation or # if some version control system is used. PROJECT_NUMBER = ver.090625 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # base path where the generated documentation will be put. # If a relative path is entered, it will be relative to the location # where doxygen was started. If left blank the current directory will be used. OUTPUT_DIRECTORY = docs # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create # 4096 sub-directories (in 2 levels) under the output directory of each output # format and will distribute the generated files over these directories. # Enabling this option can be useful when feeding doxygen a huge amount of # source files, where putting all generated files in the same directory would # otherwise cause performance problems for the file system. CREATE_SUBDIRS = NO # The OUTPUT_LANGUAGE tag is used to specify the language in which all # documentation generated by doxygen is written. Doxygen will use this # information to generate all constant output in the proper language. # The default language is English, other supported languages are # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, # Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, # Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), # Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, # Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, # Spanish, Swedish, and Ukrainian. OUTPUT_LANGUAGE = Japanese # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will # include brief member descriptions after the members that are listed in # the file and class documentation (similar to JavaDoc). # Set to NO to disable this. BRIEF_MEMBER_DESC = YES # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend # the brief description of a member or function before the detailed description. # Note if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the # brief descriptions will be completely suppressed. REPEAT_BRIEF = YES # This tag implements a quasi-intelligent brief description abbreviator # that is used to form the text in various listings. Each string # in this list, if found as the leading text of the brief description, will be # stripped from the text and the result after processing the whole list, is # used as the annotated text. Otherwise, the brief description is used as-is. # If left blank, the following values are used ("$name" is automatically # replaced with the name of the entity) "The $name class" "The $name widget" # "The $name file" "is" "provides" "specifies" "contains" # "represents" "a" "an" "the" ABBREVIATE_BRIEF = # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then # Doxygen will generate a detailed section even if there is only a brief # description. ALWAYS_DETAILED_SEC = NO # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all # inherited members of a class in the documentation of that class as if those # members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. INLINE_INHERITED_MEMB = YES # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full # path before files name in the file list and in the header files. If set # to NO the shortest path that makes the file name unique will be used. FULL_PATH_NAMES = NO # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag # can be used to strip a user-defined part of the path. Stripping is # only done if one of the specified strings matches the left-hand part of # the path. The tag can be used to show relative paths in the file list. # If left blank the directory from which doxygen is run is used as the # path to strip. STRIP_FROM_PATH = # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of # the path mentioned in the documentation of a class, which tells # the reader which header file to include in order to use a class. # If left blank only the name of the header file containing the class # definition is used. Otherwise one should specify the include paths that # are normally passed to the compiler using the -I flag. STRIP_FROM_INC_PATH = # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter # (but less readable) file names. This can be useful is your file systems # doesn t support long names like on DOS, Mac, or CD-ROM. SHORT_NAMES = NO # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen # will interpret the first line (until the first dot) of a JavaDoc-style # comment as the brief description. If set to NO, the JavaDoc # comments will behave just like regular Qt-style comments # (thus requiring an explicit @brief command for a brief description.) JAVADOC_AUTOBRIEF = NO # If the QT_AUTOBRIEF tag is set to YES then Doxygen will # interpret the first line (until the first dot) of a Qt-style # comment as the brief description. If set to NO, the comments # will behave just like regular Qt-style comments (thus requiring # an explicit \brief command for a brief description.) QT_AUTOBRIEF = NO # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen # treat a multi-line C++ special comment block (i.e. a block of //! or /// # comments) as a brief description. This used to be the default behaviour. # The new default is to treat a multi-line C++ comment block as a detailed # description. Set this tag to YES if you prefer the old behaviour instead. MULTILINE_CPP_IS_BRIEF = NO # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented # member inherits the documentation from any documented member that it # re-implements. INHERIT_DOCS = YES # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce # a new page for each member. If set to NO, the documentation of a member will # be part of the file/class/namespace that contains it. SEPARATE_MEMBER_PAGES = NO # The TAB_SIZE tag can be used to set the number of spaces in a tab. # Doxygen uses this value to replace tabs by spaces in code fragments. TAB_SIZE = 8 # This tag can be used to specify a number of aliases that acts # as commands in the documentation. An alias has the form "name=value". # For example adding "sideeffect=\par Side Effects \n" will allow you to # put the command \sideeffect (or @sideeffect) in the documentation, which # will result in a user-defined paragraph with heading "Side Effects ". # You can put \n s in the value part of an alias to insert newlines. ALIASES = # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C # sources only. Doxygen will then generate output that is more tailored for C. # For instance, some of the names that are used will be different. The list # of all members will be omitted, etc. OPTIMIZE_OUTPUT_FOR_C = NO # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java # sources only. Doxygen will then generate output that is more tailored for # Java. For instance, namespaces will be presented as packages, qualified # scopes will look different, etc. OPTIMIZE_OUTPUT_JAVA = NO # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran # sources only. Doxygen will then generate output that is more tailored for # Fortran. OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for # VHDL. OPTIMIZE_OUTPUT_VHDL = NO # Doxygen selects the parser to use depending on the extension of the files it parses. # With this tag you can assign which parser to use for a given extension. # Doxygen has a built-in mapping, but you can override or extend it using this tag. # The format is ext=language, where ext is a file extension, and language is one of # the parsers supported by doxygen IDL, Java, Javascript, C#, C, C++, D, PHP, # Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), # use inc=Fortran f=C EXTENSION_MAPPING = # If you use STL classes (i.e. std string, std vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should # set this tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std string); v.s. # func(std string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. BUILTIN_STL_SUPPORT = YES # If you use Microsoft s C++/CLI language, you should set this option to YES to # enable parsing support. CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. # Doxygen will parse them like normal C++ but will assume all classes use public # instead of private inheritance when no explicit protection keyword is present. SIP_SUPPORT = NO # For Microsoft s IDL there are propget and propput attributes to indicate getter # and setter methods for a property. Setting this option to YES (the default) # will make doxygen to replace the get and set methods by a property in the # documentation. This will only work if the methods are indeed getting or # setting a simple type. If this is not the case, or you want to show the # methods anyway, you should set this option to NO. IDL_PROPERTY_SUPPORT = YES # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC # tag is set to YES, then doxygen will reuse the documentation of the first # member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. DISTRIBUTE_GROUP_DOC = NO # Set the SUBGROUPING tag to YES (the default) to allow class member groups of # the same type (for instance a group of public functions) to be put as a # subgroup of that type (e.g. under the Public Functions section). Set it to # NO to prevent subgrouping. Alternatively, this can be done per class using # the \nosubgrouping command. SUBGROUPING = YES # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum # is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # with name TypeT. When disabled the typedef will appear as a member of a file, # namespace, or class. And the struct will be named TypeS. This can typically # be useful for C code in case the coding convention dictates that all compound # types are typedef ed and only the typedef is referenced, never the tag name. TYPEDEF_HIDES_STRUCT = NO # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to # determine which symbols to keep in memory and which to flush to disk. # When the cache is full, less often used symbols will be written to disk. # For small to medium size projects ( 1000 input files) the default value is # probably good enough. For larger projects a too small cache size can cause # doxygen to be busy swapping symbols to and from disk most of the time # causing a significant performance penality. # If the system has enough physical memory increasing the cache will improve the # performance by keeping more symbols in memory. Note that the value works on # a logarithmic scale so increasing the size by one will rougly double the # memory usage. The cache size is given by this formula # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, # corresponding to a cache size of 2^16 = 65536 symbols SYMBOL_CACHE_SIZE = 0 #---------------------------------------------------------------------------# Build related configuration options#--------------------------------------------------------------------------- # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in # documentation are documented, even if no documentation was available. # Private class members and static file members will be hidden unless # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES EXTRACT_ALL = NO # If the EXTRACT_PRIVATE tag is set to YES all private members of a class # will be included in the documentation. EXTRACT_PRIVATE = YES # If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. EXTRACT_STATIC = YES # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) # defined locally in source files will be included in the documentation. # If set to NO only classes defined in header files are included. EXTRACT_LOCAL_CLASSES = YES # This flag is only useful for Objective-C code. When set to YES local # methods, which are defined in the implementation section but not in # the interface are included in the documentation. # If set to NO (the default) only methods in the interface are included. EXTRACT_LOCAL_METHODS = YES # If this flag is set to YES, the members of anonymous namespaces will be # extracted and appear in the documentation as a namespace called # anonymous_namespace{file} , where file will be replaced with the base # name of the file that contains the anonymous namespace. By default # anonymous namespace are hidden. EXTRACT_ANON_NSPACES = YES # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all # undocumented members of documented classes, files or namespaces. # If set to NO (the default) these members will be included in the # various overviews, but no documentation section is generated. # This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_MEMBERS = NO # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all # undocumented classes that are normally visible in the class hierarchy. # If set to NO (the default) these classes will be included in the various # overviews. This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_CLASSES = NO # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all # friend (class|struct|union) declarations. # If set to NO (the default) these declarations will be included in the # documentation. HIDE_FRIEND_COMPOUNDS = NO # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any # documentation blocks found inside the body of a function. # If set to NO (the default) these blocks will be appended to the # function s detailed documentation block. HIDE_IN_BODY_DOCS = NO # The INTERNAL_DOCS tag determines if documentation # that is typed after a \internal command is included. If the tag is set # to NO (the default) then the documentation will be excluded. # Set it to YES to include the internal documentation. INTERNAL_DOCS = YES # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate # file names in lower-case letters. If set to YES upper-case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows # and Mac users are advised to set this option to NO. CASE_SENSE_NAMES = NO # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen # will show members with their full class and namespace scopes in the # documentation. If set to YES the scope will be hidden. HIDE_SCOPE_NAMES = NO # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen # will put a list of the files that are included by a file in the documentation # of that file. SHOW_INCLUDE_FILES = YES # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] # is inserted in the documentation for inline members. INLINE_INFO = YES # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen # will sort the (detailed) documentation of file and class members # alphabetically by member name. If set to NO the members will appear in # declaration order. SORT_MEMBER_DOCS = NO # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the # brief documentation of file, namespace and class members alphabetically # by member name. If set to NO (the default) the members will appear in # declaration order. SORT_BRIEF_DOCS = YES # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the # hierarchy of group names into alphabetical order. If set to NO (the default) # the group names will appear in their defined order. SORT_GROUP_NAMES = YES # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be # sorted by fully-qualified names, including namespaces. If set to # NO (the default), the class list will be sorted only by class name, # not including the namespace part. # Note This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # Note This option applies only to the class list, not to the # alphabetical list. SORT_BY_SCOPE_NAME = YES # The GENERATE_TODOLIST tag can be used to enable (YES) or # disable (NO) the todo list. This list is created by putting \todo # commands in the documentation. GENERATE_TODOLIST = YES # The GENERATE_TESTLIST tag can be used to enable (YES) or # disable (NO) the test list. This list is created by putting \test # commands in the documentation. GENERATE_TESTLIST = YES # The GENERATE_BUGLIST tag can be used to enable (YES) or # disable (NO) the bug list. This list is created by putting \bug # commands in the documentation. GENERATE_BUGLIST = YES # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or # disable (NO) the deprecated list. This list is created by putting # \deprecated commands in the documentation. GENERATE_DEPRECATEDLIST= YES # The ENABLED_SECTIONS tag can be used to enable conditional # documentation sections, marked by \if sectionname ... \endif. ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines # the initial value of a variable or define consists of for it to appear in # the documentation. If the initializer consists of more lines than specified # here it will be hidden. Use a value of 0 to hide initializers completely. # The appearance of the initializer of individual variables and defines in the # documentation can be controlled using \showinitializer or \hideinitializer # command in the documentation regardless of this setting. MAX_INITIALIZER_LINES = 50 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated # at the bottom of the documentation of classes and structs. If set to YES the # list will mention the files that were used to generate the documentation. SHOW_USED_FILES = YES # If the sources in your project are distributed over multiple directories # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy # in the documentation. The default is NO. SHOW_DIRECTORIES = NO # Set the SHOW_FILES tag to NO to disable the generation of the Files page. # This will remove the Files entry from the Quick Index and from the # Folder Tree View (if specified). The default is YES. SHOW_FILES = YES # Set the SHOW_NAMESPACES tag to NO to disable the generation of the # Namespaces page. This will remove the Namespaces entry from the Quick Index # and from the Folder Tree View (if specified). The default is YES. SHOW_NAMESPACES = YES # The FILE_VERSION_FILTER tag can be used to specify a program or script that # doxygen should invoke to get the current version for each file (typically from # the version control system). Doxygen will invoke the program by executing (via # popen()) the command command input-file , where command is the value of # the FILE_VERSION_FILTER tag, and input-file is the name of an input file # provided by doxygen. Whatever the program writes to standard output # is used as the file version. See the manual for examples. FILE_VERSION_FILTER = # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by # doxygen. The layout file controls the global structure of the generated output files # in an output format independent way. The create the layout file that represents # doxygen s defaults, run doxygen with the -l option. You can optionally specify a # file name after the option, if omitted DoxygenLayout.xml will be used as the name # of the layout file. LAYOUT_FILE = #---------------------------------------------------------------------------# configuration options related to warning and progress messages#--------------------------------------------------------------------------- # The QUIET tag can be used to turn on/off the messages that are generated # by doxygen. Possible values are YES and NO. If left blank NO is used. QUIET = NO # The WARNINGS tag can be used to turn on/off the warning messages that are # generated by doxygen. Possible values are YES and NO. If left blank # NO is used. WARNINGS = YES # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings # for undocumented members. If EXTRACT_ALL is set to YES then this flag will # automatically be disabled. WARN_IF_UNDOCUMENTED = YES # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for # potential errors in the documentation, such as not documenting some # parameters in a documented function, or documenting parameters that # don t exist or using markup commands wrongly. WARN_IF_DOC_ERROR = YES # This WARN_NO_PARAMDOC option can be abled to get warnings for # functions that are documented, but have no documentation for their parameters # or return value. If set to NO (the default) doxygen will only warn about # wrong or incomplete parameter documentation, but not about the absence of # documentation. WARN_NO_PARAMDOC = YES # The WARN_FORMAT tag determines the format of the warning messages that # doxygen can produce. The string should contain the $file, $line, and $text # tags, which will be replaced by the file and line number from which the # warning originated and the warning text. Optionally the format may contain # $version, which will be replaced by the version of the file (if it could # be obtained via FILE_VERSION_FILTER) WARN_FORMAT = "!!$file($line) $text" # The WARN_LOGFILE tag can be used to specify a file to which warning # and error messages should be written. If left blank the output is written # to stderr. WARN_LOGFILE = DoxygenLog.txt #---------------------------------------------------------------------------# configuration options related to the input files#--------------------------------------------------------------------------- # The INPUT tag can be used to specify the files and/or directories that contain # documented source files. You may enter file names like "myfile.cpp" or # directories like "/usr/src/myproject". Separate the files or directories # with spaces. INPUT = . # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is # also the default input encoding. Doxygen uses libiconv (or the iconv built # into libc) for the transcoding. See http //www.gnu.org/software/libiconv for # the list of possible encodings. INPUT_ENCODING = shift_jis # If the value of the INPUT tag contains directories, you can use the # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp # and *.h) to filter out the source-files in the directories. If left # blank the following patterns are tested # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 FILE_PATTERNS = # The RECURSIVE tag can be used to turn specify whether or not subdirectories # should be searched for input files as well. Possible values are YES and NO. # If left blank NO is used. RECURSIVE = YES # The EXCLUDE tag can be used to specify files and/or directories that should # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. EXCLUDE = # The EXCLUDE_SYMLINKS tag can be used select whether or not files or # directories that are symbolic links (a Unix filesystem feature) are excluded # from the input. EXCLUDE_SYMLINKS = NO # If the value of the INPUT tag contains directories, you can use the # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # certain files from those directories. Note that the wildcards are matched # against the file with absolute path, so to exclude all test directories # for example use the pattern */test/* EXCLUDE_PATTERNS = # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the # output. The symbol name can be a fully qualified name, a word, or if the # wildcard * is used, a substring. Examples ANamespace, AClass, # AClass ANamespace, ANamespace *Test EXCLUDE_SYMBOLS = # The EXAMPLE_PATH tag can be used to specify one or more files or # directories that contain example code fragments that are included (see # the \include command). EXAMPLE_PATH = # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp # and *.h) to filter out the source-files in the directories. If left # blank all files are included. EXAMPLE_PATTERNS = # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be # searched for input files to be used with the \include or \dontinclude # commands irrespective of the value of the RECURSIVE tag. # Possible values are YES and NO. If left blank NO is used. EXAMPLE_RECURSIVE = NO # The IMAGE_PATH tag can be used to specify one or more files or # directories that contain image that are included in the documentation (see # the \image command). IMAGE_PATH = # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program # by executing (via popen()) the command filter input-file , where filter # is the value of the INPUT_FILTER tag, and input-file is the name of an # input file. Doxygen will then use the output that the filter program writes # to standard output. If FILTER_PATTERNS is specified, this tag will be # ignored. INPUT_FILTER = # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern # basis. Doxygen will compare the file name with each pattern and apply the # filter if there is a match. The filters are a list of the form # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER # is applied to all files. FILTER_PATTERNS = # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using # INPUT_FILTER) will be used to filter the input files when producing source # files to browse (i.e. when SOURCE_BROWSER is set to YES). FILTER_SOURCE_FILES = NO #---------------------------------------------------------------------------# configuration options related to source browsing#--------------------------------------------------------------------------- # If the SOURCE_BROWSER tag is set to YES then a list of source files will # be generated. Documented entities will be cross-referenced with these sources. # Note To get rid of all source code in the generated output, make sure also # VERBATIM_HEADERS is set to NO. SOURCE_BROWSER = YES # Setting the INLINE_SOURCES tag to YES will include the body # of functions and classes directly in the documentation. INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct # doxygen to hide any special comment blocks from generated source code # fragments. Normal C and C++ comments will always remain visible. STRIP_CODE_COMMENTS = YES # If the REFERENCED_BY_RELATION tag is set to YES # then for each documented function all documented # functions referencing it will be listed. REFERENCED_BY_RELATION = NO # If the REFERENCES_RELATION tag is set to YES # then for each documented function all documented entities # called/used by that function will be listed. REFERENCES_RELATION = NO # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will # link to the source code. Otherwise they will link to the documentation. REFERENCES_LINK_SOURCE = YES # If the USE_HTAGS tag is set to YES then the references to source code # will point to the HTML generated by the htags(1) tool instead of doxygen # built-in source browser. The htags tool is part of GNU s global source # tagging system (see http //www.gnu.org/software/global/global.html). You # will need version 4.8.6 or higher. USE_HTAGS = NO # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen # will generate a verbatim copy of the header file for each class for # which an include is specified. Set to NO to disable this. VERBATIM_HEADERS = YES #---------------------------------------------------------------------------# configuration options related to the alphabetical class index#--------------------------------------------------------------------------- # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index # of all compounds will be generated. Enable this if the project # contains a lot of classes, structs, unions or interfaces. ALPHABETICAL_INDEX = NO # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns # in which this list will be split (can be a number in the range [1..20]) COLS_IN_ALPHA_INDEX = 5 # In case all classes in a project start with a common prefix, all # classes will be put under the same header in the alphabetical index. # The IGNORE_PREFIX tag can be used to specify one or more prefixes that # should be ignored while generating the index headers. IGNORE_PREFIX = #---------------------------------------------------------------------------# configuration options related to the HTML output#--------------------------------------------------------------------------- # If the GENERATE_HTML tag is set to YES (the default) Doxygen will # generate HTML output. GENERATE_HTML = YES # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `html will be used as the default path. HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for # each generated HTML page (for example .htm,.php,.asp). If it is left blank # doxygen will generate files with .html extension. HTML_FILE_EXTENSION = .html # The HTML_HEADER tag can be used to specify a personal HTML header for # each generated HTML page. If it is left blank doxygen will generate a # standard header. HTML_HEADER = # The HTML_FOOTER tag can be used to specify a personal HTML footer for # each generated HTML page. If it is left blank doxygen will generate a # standard footer. HTML_FOOTER = docs/hooter.html # The HTML_STYLESHEET tag can be used to specify a user-defined cascading # style sheet that is used by each HTML page. It can be used to # fine-tune the look of the HTML output. If the tag is left blank doxygen # will generate a default style sheet. Note that doxygen will try to copy # the style sheet file to the HTML output directory, so don t put your own # stylesheet in the HTML output directory as well, or it will be erased! HTML_STYLESHEET = docs/doxygen.css # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, # files or namespaces will be aligned in HTML using tables. If set to # NO a bullet list will be used. HTML_ALIGN_MEMBERS = YES # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the # page has loaded. For this to work a browser that supports # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). HTML_DYNAMIC_SECTIONS = NO # If the GENERATE_DOCSET tag is set to YES, additional index files # will be generated that can be used as input for Apple s Xcode 3 # integrated development environment, introduced with OSX 10.5 (Leopard). # To create a documentation set, doxygen will generate a Makefile in the # HTML output directory. Running make will produce the docset in that # directory and running "make install" will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find # it at startup. # See http //developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. GENERATE_DOCSET = NO # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the # feed. A documentation feed provides an umbrella under which multiple # documentation sets from a single provider (such as a company or product suite) # can be grouped. DOCSET_FEEDNAME = # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that # should uniquely identify the documentation set bundle. This should be a # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen # will append .docset to the name. DOCSET_BUNDLE_ID = # If the GENERATE_HTMLHELP tag is set to YES, additional index files # will be generated that can be used as input for tools like the # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) # of the generated HTML documentation. GENERATE_HTMLHELP = NO # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can # be used to specify the file name of the resulting .chm file. You # can add a path in front of the file if the result should not be # written to the html output directory. CHM_FILE = # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can # be used to specify the location (absolute path including file name) of # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run # the HTML help compiler on the generated index.hhp. HHC_LOCATION = # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag # controls if a separate .chi index file is generated (YES) or that # it should be included in the master .chm file (NO). GENERATE_CHI = NO # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING # is used to encode HtmlHelp index (hhk), content (hhc) and project file # content. CHM_INDEX_ENCODING = # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag # controls whether a binary table of contents is generated (YES) or a # normal table of contents (NO) in the .chm file. BINARY_TOC = NO # The TOC_EXPAND flag can be set to YES to add extra items for group members # to the contents of the HTML help documentation and to the tree view. TOC_EXPAND = NO # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER # are set, an additional index file will be generated that can be used as input for # Qt s qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated # HTML documentation. GENERATE_QHP = NO # If the QHG_LOCATION tag is specified, the QCH_FILE tag can # be used to specify the file name of the resulting .qch file. # The path specified is relative to the HTML output folder. QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating # Qt Help Project output. For more information please see # http //doc.trolltech.com/qthelpproject.html#namespace QHP_NAMESPACE = # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating # Qt Help Project output. For more information please see # http //doc.trolltech.com/qthelpproject.html#virtual-folders QHP_VIRTUAL_FOLDER = # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. # For more information please see # http //doc.trolltech.com/qthelpproject.html#custom-filters QHP_CUST_FILTER_NAME = # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see # a href="http //doc.trolltech.com/qthelpproject.html#custom-filters" Qt Help Project / Custom Filters /a . QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project s # filter section matches. # a href="http //doc.trolltech.com/qthelpproject.html#filter-attributes" Qt Help Project / Filter Attributes /a . QHP_SECT_FILTER_ATTRS = # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can # be used to specify the location of Qt s qhelpgenerator. # If non-empty doxygen will try to run qhelpgenerator on the generated # .qhp file. QHG_LOCATION = # The DISABLE_INDEX tag can be used to turn on/off the condensed index at # top of each HTML page. The value NO (the default) enables the index and # the value YES disables it. DISABLE_INDEX = NO # This tag can be used to set the number of enum values (range [1..20]) # that doxygen will group on one line in the generated HTML documentation. ENUM_VALUES_PER_LINE = 4 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. # If the tag value is set to FRAME, a side panel will be generated # containing a tree-like index structure (just like the one that # is generated for HTML Help). For this to work a browser that supports # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are # probably better off using the HTML help feature. Other possible values # for this tag are HIERARCHIES, which will generate the Groups, Directories, # and Class Hierarchy pages using a tree view instead of an ordered list; # ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which # disables this behavior completely. For backwards compatibility with previous # releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE # respectively. GENERATE_TREEVIEW = NONE # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be # used to set the initial width (in pixels) of the frame in which the tree # is shown. TREEVIEW_WIDTH = 6 # Use this tag to change the font size of Latex formulas included # as images in the HTML documentation. The default is 10. Note that # when you change the font size after a successful doxygen run you need # to manually remove any form_*.png images from the HTML output directory # to force them to be regenerated. FORMULA_FONTSIZE = 10 #---------------------------------------------------------------------------# configuration options related to the LaTeX output#--------------------------------------------------------------------------- # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will # generate Latex output. GENERATE_LATEX = NO # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `latex will be used as the default path. LATEX_OUTPUT = # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be # invoked. If left blank `latex will be used as the default command name. LATEX_CMD_NAME = # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to # generate index for LaTeX. If left blank `makeindex will be used as the # default command name. MAKEINDEX_CMD_NAME = # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact # LaTeX documents. This may be useful for small projects and may help to # save some trees in general. COMPACT_LATEX = NO # The PAPER_TYPE tag can be used to set the paper type that is used # by the printer. Possible values are a4, a4wide, letter, legal and # executive. If left blank a4wide will be used. PAPER_TYPE = # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX # packages that should be included in the LaTeX output. EXTRA_PACKAGES = # The LATEX_HEADER tag can be used to specify a personal LaTeX header for # the generated latex document. The header should contain everything until # the first chapter. If it is left blank doxygen will generate a # standard header. Notice only use this tag if you know what you are doing! LATEX_HEADER = # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated # is prepared for conversion to pdf (using ps2pdf). The pdf file will # contain links (just like the HTML output) instead of page references # This makes the output suitable for online browsing using a pdf viewer. PDF_HYPERLINKS = NO # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of # plain latex in the generated Makefile. Set this option to YES to get a # higher quality PDF documentation. USE_PDFLATEX = NO # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. # command to the generated LaTeX files. This will instruct LaTeX to keep # running if errors occur, instead of asking the user for help. # This option is also used when generating formulas in HTML. LATEX_BATCHMODE = NO # If LATEX_HIDE_INDICES is set to YES then doxygen will not # include the index chapters (such as File Index, Compound Index, etc.) # in the output. LATEX_HIDE_INDICES = NO #---------------------------------------------------------------------------# configuration options related to the RTF output#--------------------------------------------------------------------------- # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output # The RTF output is optimized for Word 97 and may not look very pretty with # other RTF readers or editors. GENERATE_RTF = NO # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `rtf will be used as the default path. RTF_OUTPUT = # If the COMPACT_RTF tag is set to YES Doxygen generates more compact # RTF documents. This may be useful for small projects and may help to # save some trees in general. COMPACT_RTF = NO # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated # will contain hyperlink fields. The RTF file will # contain links (just like the HTML output) instead of page references. # This makes the output suitable for online browsing using WORD or other # programs which support those fields. # Note wordpad (write) and others do not support links. RTF_HYPERLINKS = NO # Load stylesheet definitions from file. Syntax is similar to doxygen s # config file, i.e. a series of assignments. You only have to provide # replacements, missing definitions are set to their default value. RTF_STYLESHEET_FILE = # Set optional variables used in the generation of an rtf document. # Syntax is similar to doxygen s config file. RTF_EXTENSIONS_FILE = #---------------------------------------------------------------------------# configuration options related to the man page output#--------------------------------------------------------------------------- # If the GENERATE_MAN tag is set to YES (the default) Doxygen will # generate man pages GENERATE_MAN = NO # The MAN_OUTPUT tag is used to specify where the man pages will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `man will be used as the default path. MAN_OUTPUT = # The MAN_EXTENSION tag determines the extension that is added to # the generated man pages (default is the subroutine s section .3) MAN_EXTENSION = # If the MAN_LINKS tag is set to YES and Doxygen generates man output, # then it will generate one additional man file for each entity # documented in the real man page(s). These additional files # only source the real man page, but without them the man command # would be unable to find the correct page. The default is NO. MAN_LINKS = NO #---------------------------------------------------------------------------# configuration options related to the XML output#--------------------------------------------------------------------------- # If the GENERATE_XML tag is set to YES Doxygen will # generate an XML file that captures the structure of # the code including all documentation. GENERATE_XML = NO # The XML_OUTPUT tag is used to specify where the XML pages will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `xml will be used as the default path. XML_OUTPUT = # The XML_SCHEMA tag can be used to specify an XML schema, # which can be used by a validating XML parser to check the # syntax of the XML files. XML_SCHEMA = # The XML_DTD tag can be used to specify an XML DTD, # which can be used by a validating XML parser to check the # syntax of the XML files. XML_DTD = # If the XML_PROGRAMLISTING tag is set to YES Doxygen will # dump the program listings (including syntax highlighting # and cross-referencing information) to the XML output. Note that # enabling this will significantly increase the size of the XML output. XML_PROGRAMLISTING = NO #---------------------------------------------------------------------------# configuration options for the AutoGen Definitions output#--------------------------------------------------------------------------- # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will # generate an AutoGen Definitions (see autogen.sf.net) file # that captures the structure of the code including all # documentation. Note that this feature is still experimental # and incomplete at the moment. GENERATE_AUTOGEN_DEF = YES #---------------------------------------------------------------------------# configuration options related to the Perl module output#--------------------------------------------------------------------------- # If the GENERATE_PERLMOD tag is set to YES Doxygen will # generate a Perl module file that captures the structure of # the code including all documentation. Note that this # feature is still experimental and incomplete at the # moment. GENERATE_PERLMOD = NO # If the PERLMOD_LATEX tag is set to YES Doxygen will generate # the necessary Makefile rules, Perl scripts and LaTeX code to be able # to generate PDF and DVI output from the Perl module output. PERLMOD_LATEX = NO # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be # nicely formatted so it can be parsed by a human reader. This is useful # if you want to understand what is going on. On the other hand, if this # tag is set to NO the size of the Perl module output will be much smaller # and Perl will parse it just the same. PERLMOD_PRETTY = NO # The names of the make variables in the generated doxyrules.make file # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. # This is useful so different doxyrules.make files included by the same # Makefile don t overwrite each other s variables. PERLMOD_MAKEVAR_PREFIX = #---------------------------------------------------------------------------# Configuration options related to the preprocessor #--------------------------------------------------------------------------- # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will # evaluate all C-preprocessor directives found in the sources and include # files. ENABLE_PREPROCESSING = YES # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro # names in the source code. If set to NO (the default) only conditional # compilation will be performed. Macro expansion can be done in a controlled # way by setting EXPAND_ONLY_PREDEF to YES. MACRO_EXPANSION = NO # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES # then the macro expansion is limited to the macros specified with the # PREDEFINED and EXPAND_AS_DEFINED tags. EXPAND_ONLY_PREDEF = NO # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files # in the INCLUDE_PATH (see below) will be search if a #include is found. SEARCH_INCLUDES = YES # The INCLUDE_PATH tag can be used to specify one or more directories that # contain include files that are not input files but should be processed by # the preprocessor. INCLUDE_PATH = # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard # patterns (like *.h and *.hpp) to filter out the header-files in the # directories. If left blank, the patterns specified with FILE_PATTERNS will # be used. INCLUDE_FILE_PATTERNS = # The PREDEFINED tag can be used to specify one or more macro names that # are defined before the preprocessor is started (similar to the -D option of # gcc). The argument of the tag is a list of macros of the form name # or name=definition (no spaces). If the definition and the = are # omitted =1 is assumed. To prevent a macro definition from being # undefined via #undef or recursively expanded use the = operator # instead of the = operator. PREDEFINED = # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then # this tag can be used to specify a list of macro names that should be expanded. # The macro definition that is found in the sources will be used. # Use the PREDEFINED tag if you want to use a different macro definition. EXPAND_AS_DEFINED = # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then # doxygen s preprocessor will remove all function-like macros that are alone # on a line, have an all uppercase name, and do not end with a semicolon. Such # function macros are typically used for boiler-plate code, and will confuse # the parser if not removed. SKIP_FUNCTION_MACROS = YES #---------------------------------------------------------------------------# Configuration additions related to external references #--------------------------------------------------------------------------- # The TAGFILES option can be used to specify one or more tagfiles. # Optionally an initial location of the external documentation # can be added for each tagfile. The format of a tag file without # this location is as follows # TAGFILES = file1 file2 ... # Adding location for the tag files is done as follows # TAGFILES = file1=loc1 "file2 = loc2" ... # where "loc1" and "loc2" can be relative or absolute paths or # URLs. If a location is present for each tag, the installdox tool # does not have to be run to correct the links. # Note that each tag file must have a unique name # (where the name does NOT include the path) # If a tag file is not located in the directory in which doxygen # is run, you must also specify the path to the tagfile here. TAGFILES = # When a file name is specified after GENERATE_TAGFILE, doxygen will create # a tag file that is based on the input files it reads. GENERATE_TAGFILE = # If the ALLEXTERNALS tag is set to YES all external classes will be listed # in the class index. If set to NO only the inherited external classes # will be listed. ALLEXTERNALS = NO # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed # in the modules index. If set to NO, only the current project s groups will # be listed. EXTERNAL_GROUPS = YES # The PERL_PATH should be the absolute path and name of the perl script # interpreter (i.e. the result of `which perl ). PERL_PATH = #---------------------------------------------------------------------------# Configuration options related to the dot tool #--------------------------------------------------------------------------- # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base # or super classes. Setting the tag to NO turns the diagrams off. Note that # this option is superseded by the HAVE_DOT option below. This is only a # fallback. It is recommended to install and use dot, since it yields more # powerful graphs. CLASS_DIAGRAMS = YES # You can define message sequence charts within doxygen comments using the \msc # command. Doxygen will then run the mscgen tool (see # http //www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the # documentation. The MSCGEN_PATH tag allows you to specify the directory where # the mscgen tool resides. If left empty the tool is assumed to be found in the # default search path. MSCGEN_PATH = # If set to YES, the inheritance and collaboration graphs will hide # inheritance and usage relations if the target is undocumented # or is not a class. HIDE_UNDOC_RELATIONS = YES # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is # available from the path. This tool is part of Graphviz, a graph visualization # toolkit from AT T and Lucent Bell Labs. The other options in this section # have no effect if this option is set to NO (the default) HAVE_DOT = YES # By default doxygen will write a font called FreeSans.ttf to the output # directory and reference it in all dot files that doxygen generates. This # font does not include all possible unicode characters however, so when you need # these (or just want a differently looking font) you can specify the font name # using DOT_FONTNAME. You need need to make sure dot is able to find the font, # which can be done by putting it in a standard location or by setting the # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory # containing the font. DOT_FONTNAME = Tahoma # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. # The default size is 10pt. DOT_FONTSIZE = 8 # By default doxygen will tell dot to use the output directory to look for the # FreeSans.ttf font (which doxygen will put there itself). If you specify a # different font using DOT_FONTNAME you can set the path where dot # can find it using this tag. DOT_FONTPATH = "E \Program Files\Graphviz2.22\etc\fonts\tahoma.ttf" # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen # will generate a graph for each documented class showing the direct and # indirect inheritance relations. Setting this tag to YES will force the # the CLASS_DIAGRAMS tag to NO. CLASS_GRAPH = YES # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen # will generate a graph for each documented class showing the direct and # indirect implementation dependencies (inheritance, containment, and # class references variables) of the class with other documented classes. COLLABORATION_GRAPH = YES # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen # will generate a graph for groups, showing the direct groups dependencies GROUP_GRAPHS = YES # If the UML_LOOK tag is set to YES doxygen will generate inheritance and # collaboration diagrams in a style similar to the OMG s Unified Modeling # Language. UML_LOOK = YES # If set to YES, the inheritance and collaboration graphs will show the # relations between templates and their instances. TEMPLATE_RELATIONS = NO # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT # tags are set to YES then doxygen will generate a graph for each documented # file showing the direct and indirect include dependencies of the file with # other documented files. INCLUDE_GRAPH = YES # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and # HAVE_DOT tags are set to YES then doxygen will generate a graph for each # documented header file showing the documented files that directly or # indirectly include this file. INCLUDED_BY_GRAPH = YES # If the CALL_GRAPH and HAVE_DOT options are set to YES then # doxygen will generate a call dependency graph for every global function # or class method. Note that enabling this option will significantly increase # the time of a run. So in most cases it will be better to enable call graphs # for selected functions only using the \callgraph command. CALL_GRAPH = YES # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then # doxygen will generate a caller dependency graph for every global function # or class method. Note that enabling this option will significantly increase # the time of a run. So in most cases it will be better to enable caller # graphs for selected functions only using the \callergraph command. CALLER_GRAPH = YES # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen # will graphical hierarchy of all classes instead of a textual one. GRAPHICAL_HIERARCHY = YES # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES # then doxygen will show the dependencies a directory has on other directories # in a graphical way. The dependency relations are determined by the #include # relations between the files in the directories. DIRECTORY_GRAPH = YES # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images # generated by dot. Possible values are png, jpg, or gif # If left blank png will be used. DOT_IMAGE_FORMAT = png # The tag DOT_PATH can be used to specify the path where the dot tool can be # found. If left blank, it is assumed the dot tool can be found in the path. DOT_PATH = "../../../../Program Files/Graphviz2.22/bin" # The DOTFILE_DIRS tag can be used to specify one or more directories that # contain dot files that are included in the documentation (see the # \dotfile command). DOTFILE_DIRS = # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of # nodes that will be shown in the graph. If the number of nodes in a graph # becomes larger than this value, doxygen will truncate the graph, which is # visualized by representing a node as a red box. Note that doxygen if the # number of direct children of the root node in a graph is already larger than # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. DOT_GRAPH_MAX_NODES = 30 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the # graphs generated by dot. A depth value of 3 means that only nodes reachable # from the root by following a path via at most 3 edges will be shown. Nodes # that lay further from the root node will be omitted. Note that setting this # option to 1 or 2 may greatly reduce the computation time needed for large # code bases. Also note that the size of a graph can be further restricted by # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. MAX_DOT_GRAPH_DEPTH = 5 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent # background. This is disabled by default, because dot on Windows does not # seem to support this out of the box. Warning Depending on the platform used, # enabling this option may lead to badly anti-aliased labels on the edges of # a graph (i.e. they become hard to read). DOT_TRANSPARENT = YES # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output # files in one run (i.e. multiple -o and -T options on the command line). This # makes dot run faster, but since only newer versions of dot ( 1.8.10) # support this, this feature is disabled by default. DOT_MULTI_TARGETS = YES # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will # generate a legend page explaining the meaning of the various boxes and # arrows in the dot generated graphs. GENERATE_LEGEND = YES # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will # remove the intermediate dot files that are used to generate # the various graphs. DOT_CLEANUP = YES #---------------------------------------------------------------------------# Options related to the search engine#--------------------------------------------------------------------------- # The SEARCHENGINE tag specifies whether or not a search engine should be # used. If set to NO the values of all tags below this one will be ignored. SEARCHENGINE = YES
https://w.atwiki.jp/saigasikito/pages/9.html
@wikiにはいくつかの便利なプラグインがあります。 アーカイブ コメント ニュース 人気商品一覧 動画(Youtube) 編集履歴 関連ブログ これ以外のプラグインについては@wikiガイドをご覧ください = http //atwiki.jp/guide/
https://w.atwiki.jp/himejishi/pages/188.html
高見 千咲（たかみ ちさき） 公式サイト https //www.chisakitakami.com（リンク切れ） ブログ ツイッター https //twitter.com/chisakitakami フェイスブック https //www.facebook.com/chisaki.takami フェイスブックページ https //www.facebook.com/profile.php?id=100087806086086 https //www.facebook.com/profile.php?id=100089949344803 インスタグラム https //www.instagram.com/chisakitakami https //www.instagram.com/chisakitakamisupporters ユーチューブ ティックトック https //www.tiktok.com/@chisakitakami 選挙ドットコム https //go2senkyo.com/seijika/185783 所属 党派…自由民主党 会派…自由民主党 出身 兵庫県姫路市 https //www.chisakitakami.com/ ニュース検索結果 https //news.ritlweb.com/search/%22%E9%AB%98%E8%A6%8B%E5%8D%83%E5%92%B2%22 当選回数 1回
https://w.atwiki.jp/albali/pages/43.html
Promotion Movie http //www.nicovideo.jp/watch/sm6406479 名前 コメント
https://w.atwiki.jp/cod4mod/pages/47.html
Articles in category "Call of Duty 4 Modern Warfare" Cod4 Compile Tools について CoD4 Map light settings CoD4 Steam版日本語アップグレード導入方法 Creating a Custom Intro Screen Creating a custom minimap image Creating a Custom Video Creating a grid file Direct Light Editing Terrain Frequently Asked Questions ( FAQ ) Gameplay standards Lighting List Of Animations Making a custom MP load screen Making a room Models in Radiant MP Game Script Files MP Map Checklist MP Mapping MP Zone Files Prefabs Radiant Basics Reflection Probes Script Commands Scripting Basics Tool Textures World Textures ミニマップを作ろう！ ロードスクリーンを作ろう！ (Original "http //www.infinityward.com/wiki/index.php?title=Category Call_of_Duty_4 _Modern_Warfare") 名前 すべて読む
https://w.atwiki.jp/saigasikito/pages/6.html
更新履歴 @wikiのwikiモードでは #recent(数字) と入力することで、wikiのページ更新履歴を表示することができます。 詳しくはこちらをご覧ください。 ＝＞http //atwiki.jp/guide/17_117_ja.html たとえば、#recent(20)と入力すると以下のように表示されます。 取得中です。